Honest limits

What Aggrete does not stop.

Credibility beats coverage. These are the classes of 2025 and 2026 incidents where a policy proxy is the wrong control, so nobody adopts Aggrete for a problem it does not solve. Of the fourteen widely discussed incidents we scored, nine fall here. The scored list names each one.

classexampleswhy a proxy cannot helpthe right control
Supply chainA worm on the MCP Registry; plugin pins not verified; SDK transport flawsThe compromise is the install, before any call is madeRegistry vetting, dependency scanning, pinned installs
Host executionGit hooks running when an agent touches a repositoryNo tool call is involvedThe agent vendor's sandbox
Client-side exfiltrationA token leaked through a URL the client downloads itselfThe client acts without an MCP callThe client vendor's fix
Client-side policy bugsA deny rule that silently stops applyingA policy inside the client fails with the clientEnforce outside the process, which is what a proxy is; it still cannot patch the client
Memory poisoningPersistent instructions planted in assistant memoryThe memory is the assistant's; no proxy sees itAssistant vendors; the flow rule only limits what a poisoned session can send out
Open portsServers on the internet with no authenticationSomeone else's misconfigurationaggrete scan flags configs with no auth; closing the port is theirs
Raw shells and credentials on diskA coding agent using a token it found in a file, through a CLINot a tool call; the proxy never sees itSecret scanning, least-privilege tokens, sandboxes

What it does stop, with runnable evidence

The combination of allowed reads that forms a leak. The write that follows an untrusted read. Poisoned tool descriptions, and tools that change after approval. Credentials in tool arguments. Results that describe too few people. Bulk extraction. And any of these under a rule that holds for a person's sign-off. Every one is a check you can rerun: the conformance report.

The honest summary of the 2026 record: a proxy would have stopped or blunted about a third of the widely discussed incidents, the third that passed every permission check. The rest belong to scanners and platform vendors. Aggrete should sit next to them, not instead of them.
Open source

Deterministic policy for what AI can reach and do.

Aggrete is Apache-2.0. No model in the decision path.

Star on GitHub How it works