Nice work shipping this.<p>Disclosure: author of a related tool here. I have create agent-vault-proxy for a very similar reason. It also can help keep credentials out of the agent process. The agent gets a placeholder, the proxy swaps in the real secret in transit.<p>I read them as complementary: action firewall in front, credential broker behind.
<a href="https://github.com/inflightsec/agent-vault-proxy" rel="nofollow">https://github.com/inflightsec/agent-vault-proxy</a>
This is very interesting. I build something like this but native to claude code and something that focus on just logging the violation. My question is if you are terminating a process with in the workflow will that about all other things that executed before. anyway would love your feed back on this <a href="https://github.com/varmabudharaju/agent-pd" rel="nofollow">https://github.com/varmabudharaju/agent-pd</a>
This is a really cool library to look at even if you aren't running openclaw directly.<p>Lots of good concepts to seek inspiration from.<p>1. process-scoped egress policy<p>2. policy-as-code<p>3. explicit approval classes<p>4. normalized network/ guardrail receipts.<p>5. structured guardrail outcomes<p>6. centralized decision rules
How will credentials be injected via Gateway for each user ? If we have 5 users with one gateway, how it knows whose github credential to inject ?
I did this
Neat! Reading the docs - it's default-allow and ships with no rules? Any plans for a default rule set?
really interesting work! i am curious how you handle rule configuration for different protocols such as Postgres or ssh.
Thanks for open-sourcing it under MIT.
[flagged]