Find
Every agent, tool and MCP server in your code, and the places where one hidden instruction could send data out.
AgentFox stops attacks without stopping the people your agent is there to help.
No account. No API key. Open source under Apache-2.0.
AgentFox reads your repository, finds every agent and the tools each one can reach, and drafts the rules from that. You review them. You don't write them.
Every agent, tool and MCP server in your code, and the places where one hidden instruction could send data out.
Each agent is allowed the tools its code already uses, and nothing else. The risky ones are marked for you to confirm.
One line in your entry point, or a hook for a coding agent. From the next run every call is recorded. Nothing is blocked until you say so.
uvx agentfox scanOr connect GitHub and scan in the browser “Cancel”, “override”, “ignore”. A filter trained on attack wording blocks the customer too.
Each model at its default setting.
No guardrail is perfect. So no rule blocks anyone until you have seen what it would block.
New rules run on live traffic and record what they would block. Nobody is blocked yet.
Run a rule over past conversations. See every message it would have stopped, before a customer does.
Turn on the rules that held up. A false alarm becomes an exception that expires, not a switched-off rule.
Open-source governance toolkits are good libraries. They leave the inventory, the policy and the rollout to your engineers.
Tested on 339 harmless messages written to look like attacks, and 60 real attacks.
NotInject, 339 messages
deepset held-out, 60 attacks
A false block is a customer who didn't get help, and a ticket for your team.
Changes, cancellations and refunds are the job. They shouldn't look like attacks.
If enforcement was switched off after it blocked customers, replay your rules and turn them back on.
One command finds your agents. It starts in watch mode, so nothing is blocked until you say so.
uvx agentfox scan