Fabraix Red Team Playground
Free · Open source
AI security researchers
Your agents have two access states: full account access or nothing — and when something goes wrong, there's no log of what they actually did or why.
Agent Passport is an open-source authorization layer that sits between your agents and the actions they take. You issue a scoped passport — specific permissions, a spend cap, a time window — then every action checks against it before executing. Denied calls are logged alongside allowed ones, so you have a record either way. Delegation chains shrink permissions as they pass down to sub-agents; a child passport cannot exceed what the parent granted. Revocation cascades instantly across the whole chain, so you're not hunting down API keys across six services.
Bottom line: Pick this when you need spend limits and a signed audit trail before your LangChain or CrewAI agents touch production systems — but if your compliance requirement calls for a managed audit store with access controls rather than a self-hosted SQLite file, you'll need to build that layer yourself.
Find your fit
More options in Guardrails & Safety. Compare pricing, platforms, and features side by side.
Free · Open source
AI security researchers
Freemium
Legal professionals handling confidential cases
Most agent stacks treat authorization as an afterthought: identity tells you who the agent is, but nothing enforces what it can do, how much it can spend, or when to cut it off. Agent Passport fills that gap with three API calls — issue, authorize, delegate. You issue a signed passport scoped to a specific agent, action set, budget cap, and time-to-live. Every subsequent action calls authorize() before executing; the result is either allowed or denied, and both outcomes are logged. When an agent needs to hand off work to a sub-agent, delegate() produces a narrower passport — permissions only shrink, never grow.
The audit trail is the differentiating feature for teams with compliance requirements. Every authorize() call is persisted in SQLite and queryable by passport ID, with the action, agent identity, timestamp, and denial reason all captured. The sample output in the docs shows denied calls like ‘payment:charge exceeds $500 budget’ and ‘database:drop permission not granted’ sitting in the same log as allowed ones — which means your audit record reflects what agents attempted, not just what succeeded.
The tool fits cleanly into stacks already using LangChain, CrewAI, Express, Fastify, or the Model Context Protocol, with purpose-built packages for each. The self-hosted server package runs a REST API with SQLite and a dashboard, and the MIT license means no vendor dependency. Where it shows its limits: the audit store is SQLite, so teams with high-volume agent workloads or multi-instance deployments will hit the ceiling of a single-file database and need to replace or wrap that layer. Teams whose compliance requirements mandate a managed, access-controlled audit log — not a local SQLite file — will find they’re maintaining infrastructure Agent Passport does not provide.
Installation is via npm (@passport-agent/sdk is the main entry point), and the vendor states the full API surface is three verbs. Eight packages cover the integration surface: core token and policy engine, SDK, middleware for Node.js frameworks, wrappers for LangChain and CrewAI, A2A Protocol extensions, MCP middleware, and the self-hosted authority server. The protocol spec is open, and the project is MIT licensed with source on GitHub.
Sign in to rate this tool or suggest an edit.