How it works
From first agent to enforced policy in four steps.
Put the gateway in front of your MCP servers, give every agent an owner and a scope, watch what would be blocked, then enforce. The same steps work from the console, the REST API, the TypeScript SDK and the GitHub Action.
- 01
Put the gateway in front of your MCP servers
Register each MCP server your agents use. Agent calls go through AtmanID, which checks them before forwarding.
- 02
Give every agent an owner and a scope
Register agents in the console, through the API or from a GitOps manifest. Each gets a short-lived token for the tools it may call, and a person accountable for it.
- 03
Watch in shadow mode
New servers start in shadow: every call is checked and logged, and what would have been blocked shows as a would-deny — nothing breaks.
- 04
Enforce, and prove it
Switch a server to enforce after a preview of what it will block. Every allow and deny lands on the tamper-evident audit trail, ready for an evidence pack.
you > grant me admin on github-prod
iris > Denied. Your role (End User) does not hold GRANT on github-prod.
• Same policy decision point as POST /api/v1/* — I can’t exceed your access
• Logged: POLICY_DENY · audit ref req_c41a…
• Opened REQ-0231 instead — approver dev.torres (owner) · SoD check clean
Denials are evidence too — every one is queryable.
1,284 calls checked
Would have been blocked
- Tool outside the agent’s scope9
- Agent over its rate limit3
Agents affected: Deploy Bot, Release Notes Agent. These calls went through while in shadow mode.
Next: switch to enforce. Every decision is recorded on the audit trail.
Pick your next step.
Talk to us
Direct line to the founder. Best for technical evaluation, custom-control questions, or pilot scoping.
hello@atmanid.com
Browse the developer portal
OpenAPI 3.1 spec, interactive explorer, GitHub Action recipe, MCP integration. No login required.
Open /developers
Request a security review
Questionnaire answers and an architecture walkthrough under NDA. No SOC 2 report yet — we say so up front.
Request a review
Read security commitments
Public Trust page: subprocessors, security architecture, certifications, customer obligations.
Open /trust