durin
Sign up
▣ ✻ Claude Code

Try an MCP request.

See what an agent is allowed to do. Run a sample 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

  1. YouPrompt

    Read the engineering handbook through Durin and summarize the release rule.

  2. ClaudeThinking

    I need the handbook. I will call the governed MCP tool and let Durin check identity, policy, and scope first.

  3. Tool useMCP call

    mcp__durin__sandbox__read_document({ "resource": "engineering/handbook", "durinIdempotencyKey": "demo-read-001" })

  4. Durin MCPPolicy check

    ALLOW: Policy matched an approved read. No approval required.

  5. Tool resultSandbox response

    Synthetic handbook: Engineering changes require a review before release.

  6. ClaudeFinal answer

    The handbook says engineering changes require review before release.

Press Enter to run the prefilled command. If you do nothing, it plays automatically.

Fake Claude Code terminal showing the model prompt, reasoning summary, MCP tool call, Durin decision, and final answer.

Read allowed.

The sample member is active and the requested document is approved. The example response contains handbook text.

Reset simulation
Sample identity
Demo member · active
Policy decision
Allowed · policy v1
Decision reason
approved_resource_read
Approval
Not required for this read

Demonstration only. Identity and provider trust states are fixed fixtures. Results and approvals are not stored, and no real tool or audit record is created.

Inspect the sample MCP messages

Review the tools/call request and response shape behind the selected path.

Request

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "sandbox__read_document",
    "arguments": {
      "resource": "engineering/handbook",
      "durinIdempotencyKey": "demo-read-001"
    }
  }
}

Response

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "content": [
      {
        "type": "text",
        "text": "Synthetic handbook: Engineering changes require a review before release."
      }
    ],
    "isError": false
  }
}
Read the MCP tools specification

From a sample to your own workflow.

  1. Try the three outcomes

    Compare a permitted read, a write that needs approval, and revoked access. Inspect the example MCP messages behind each result.

  2. Evaluate in a workspace

    Sign up to explore authenticated connection ownership, approval review, and audit records.

  3. 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. This public simulator uses fixed sample identities, tools, and data. Choose a scenario and run it on this page, including with JavaScript disabled.

Does this call a real MCP server?

The website illustrates the same policy and approval-matching model used by Durin’s gateway. The real gateway remains authenticated and records governed request activity.

Does a simulated approval grant access to a real system?

No. It only demonstrates an exact-match approval with a fixed sample reviewer and time. A real request needs current identity, policy, independent approval where required, and the connected system’s own permissions.

Evaluate your own governed workflow.

Create an account after trying the public simulator to evaluate governed requests, approvals, and audit with your admins.

Create an account

Production connections use provider setup and trust review.