Every action has a boundary.

Follow a governed agent request from identity and policy through approval, execution, and attributable evidence.

Durin admin console showing requested MCP connections and their review status — Give administrators one place to review connection requests.

See what happens before and after the call.

Durin evaluates a request at the point where an approved agent asks to use a connected system. Policy can allow, deny, or require approval; a dispatched call can then succeed, fail, or remain uncertain.

Identify the request
Carry organization, environment, requesting person or service, authenticated client, connection, tool, and resource context into the decision. A self-reported client name is metadata, not permission.
Evaluate the policy
Default allow follows membership, client restrictions, connection and resource policy, reviewed capability mappings, and the upstream credential boundary.
Execute and record
Record intent before dispatch and store the outcome. Exact approvals bind arguments, schema and policy version, requesting identity, resource set, expiry, and execution count.