AgentGate vs Presidio

AgentGate

An agent or its host can send each tool call to one REST endpoint, or wrap an MCP server, and get allow, deny or ask from a local classifier and a YAML policy, with an audit log and approval queue. The project is three days old, auth is off by default, and no detection accuracy is published.

Presidio

MIT-licensed personal data detector with a public OpenAPI document, tests on Python 3.10 to 3.14 and about 1.2 million weekly PyPI downloads. The REST containers have no authentication, the project states no SLA or support, and it covers personal data only, with no prompt injection or content moderation checks.

AgentGate

1. Create a session with the user's real goal first. The goal-alignment head scores every later call against it
2. Pass earlier tool results in history_override with untrusted: true for web or email content, or the injection head sees only the action
3. On ask, stop and tell the user the decision_id. Polling /v1/decisions/:id needs the dashboard key
4. Treat allow_with_checkpoint as allow and keep the checkpoint_id for an undo
5. Expect HTTP 404 with not_found for an unknown session and 401 when the owner has set an agent key

Presidio

1. Install from PyPI or pull images from ghcr.io/data-privacy-stack. The mcr.microsoft.com/presidio-* images are no longer updated
2. Download a spaCy model (python -m spacy download en_core_web_lg) before the first AnalyzerEngine() call, or use the Docker image
3. Send both text and language to /analyze. A request missing either returns HTTP 500 with a JSON error field
4. Pass entities and score_threshold to limit results. Many country-specific recognisers are disabled by default and need enabling in the registry YAML
5. Keep the containers on a private network or behind your own authenticating proxy. They accept any caller