Bring agent access under your control.
Use Durin’s MCP proxy to give AI agents a managed path to company systems. Set permissions, approve sensitive actions, and review what happened.
An action. A decision.
Permission is evaluated before a tool runs.
Different responsibilities. One shared view.
IT manages the path. Security sets the rules. Platform teams maintain the connections. Compliance follows the evidence. Start with the job your team needs to do.
Bring agent access under IT control.
Give employees an approved route to company systems. Review requests on that route and test direct connections separately.
Plan the IT rolloutIllustrative workflow
A support agent reads assigned tickets through the approved endpoint while IT tests an older local connector separately.
What to verify
- Approved client configured
- Direct routes tested
- Access owner assigned
Approve the action, not a blank check.
Require a separate approval for a sensitive write. Connect the request to the person, policy, and result behind it.
Review security controlsIllustrative workflow
An agent may read assigned tickets, but updating one issue waits for approval of that exact change.
What to verify
- Sensitive write identified
- Exact approval required
- Execution result reviewed
Apply consistent rules as tools change.
Give platform teams a repeatable way to review tools, connection permissions, and policy changes before use.
Design the platform pathIllustrative workflow
An upstream tool changes its accepted inputs. The platform team reviews the new tool definition before making it available to clients.
What to verify
- Tool changes reviewed
- Provider consent scoped
- Failure handling tested
Answer who did what, and why.
Follow a request from identity and policy through approval and result. Give reviewers a connected record with clear retention limits.
Evaluate evidence workflowsIllustrative workflow
A reviewer traces a sample request, checks the policy decision and any approval, and reviews the recorded execution outcome.
What to verify
- Identity linked
- Decision and outcome recorded
- Retention limits defined
Start with one useful workflow.
Pick one use case
Choose one client, one company system, and one owner. Agree on the intended result and when to stop.
Test the workflow
Use governed requests to test allowed access, denied actions, approvals, and revocation. Inspect the record, including uncertain results.
Plan a live rollout
Review provider consent, identity, network coverage, retention, and recovery with the teams who will operate the connection.
Choose your first governance workflow.
Create an account to manage a bounded workflow for IT, security, platform engineering, or compliance.
Create an accountProduction connections use provider setup and trust review.