Try an MCP request.
See what an agent is allowed to do. Run an MCP request through Durin’s policy checks without an account or API key.
Claude Code v2.1.278
Fable 5.1 with high effort · Claude Max
/Users/durin
⚠ 1 MCP server needs authentication · run /mcp
Follow the decision.
Choose a request above, then run the simulation. You’ll see the policy result, approval requirement, and MCP messages here.
From the simulator to your own workflow.
Try the three outcomes
Compare a permitted read, a write that needs approval, and revoked access. Inspect the MCP messages behind each result.
Evaluate in a workspace
Book a demo to explore authenticated connection ownership, approval review, and audit records.
Verify before going live
Check your client, identity, provider permissions, data boundaries, and production trust controls before connecting a live system.
What this workflow lets you test.
Do I need an account or API key?
No. Choose a scenario and run it on this page, even with JavaScript disabled.
Does this call a real MCP server?
No. It runs the same policy and approval-matching checks as Durin’s gateway. The gateway requires authentication and records governed request activity.
Does a simulated approval grant access to a real system?
No. It shows how Durin matches an approval to the exact request. A live request needs current identity, policy, independent approval where required, and the connected system’s own permissions.
Evaluate your own governed workflow.
Book a demo to explore agent access, policy checks, approvals, and audit records with our team.
Book a demo