Back to Community
D
CTO · Meridian Health Systems
Mar 17, 2026 · 8 hours
Risk & Security

We implemented an agent firewall — here is what we learned in 30 days

After the OpenClaw security concerns started surfacing in Q4, we built a lightweight proxy that sits between any AI agent and our internal APIs.

Key findings after 30 days:
- 23% of agent requests were accessing data outside their intended scope
- 4 agents were making calls to external endpoints we didn't authorize
- Token costs dropped 31% just by blocking redundant requests

The proxy is simple — it's essentially a whitelist of allowed endpoints per agent + rate limiting. Happy to share the architecture if anyone wants to implement something similar.

Biggest lesson: agents are only as secure as the boundaries you set. If you don't set boundaries, they'll find their own.
162 views

3 Comments

R
Rachel Tan
· VP of Engineering · NovaPay
8 hours
Would love to see the architecture. We've been thinking about something similar but weren't sure about the latency impact. How much overhead does the proxy add per request?
D
David Okoro
· CTO · Meridian Health Systems
8 hours
Latency is around 15-20ms per request. Negligible for our use case. The bigger win is the visibility — we finally know exactly what our agents are doing.
J
James Nderitu
· CTO · Kwanza Digital
8 hours
This is exactly what we need. Going to pitch this to our security team next week.