durin
Book A Demo

A trusted employee. An overprivileged agent.

A CISO guide to unmanaged agent access, MCP Governance boundaries, prompt injection, and production gates.

The decision in brief

Apply MCP Governance to a known route, then assess the residual risks around content, clients, providers, and bypass.

Start with the observation boundary

Security reviews often begin with the word “agent” as if it names one controlled system. In practice, an agent may combine a model, client, local server, remote MCP server, browser, and upstream credentials. A proxy governs the requests that reach its endpoint. That boundary is valuable precisely because it is specific.

State what is outside it: direct provider calls, unmanaged clients, browser actions, shell commands, and model-provider handling of returned tool results. This makes the control review honest and directs compensating controls to the right owners.

A convincing tool result

A routed tool returns a document containing instructions that tell the model to disable a control or reveal data. The proxy can still require identity, policy, and approval before a write, but it cannot decide whether every piece of content is trustworthy.

Prompt injection defenses belong across the model, client, application, and human approval path. Treat a proxy as one layer in defense in depth, with production gates for dangerous actions and a way to inspect uncertain outcomes.

Anthropic: prompt-injection defenses

Security review checklist

Ask for evidence that maps the control to a request and its outcome:

  • Is identity verified at the final authorization check, including current membership or revocation?
  • Are upstream credentials scoped to the connection and audience, with consent kept distinct from gateway login?
  • Are tool and resource mappings reviewed, versioned, and denied when coverage is unknown?
  • Are sensitive writes independently approved against exact arguments, schema, policy, expiry, and use count?
  • Does the audit record distinguish policy outcome from execution outcome, including uncertainty?
  • Can the team demonstrate direct-path and bypass testing for the intended deployment?

What Durin covers

Durin’s governed path covers default-allow authorization checks, optional write review or disallow controls, scoped connections, and audit. Enterprise uptime and support commitments are defined in the customer agreement. Public trust copy does not claim certification or a residency guarantee.

That distinction is useful in a CISO review: evaluate the decision model and evidence path, then verify identity, provider, network, retention, recovery, and operational proof for the production path.

Durin security controlsDurin production trust

Questions for a security evaluation.

Does MCP Governance solve prompt injection?

No. Prompt injection remains an active model and application risk. Durin enforces routed access policy and approvals; application owners still need input handling, model defenses, and production gates.

What evidence should security request?

Request identity, client, connection, policy decision, approval, dispatch, outcome, revocation, and coverage evidence, with retention and provider boundaries stated explicitly.

Test the control boundary.

Book a demo to explore agent access, policy checks, approvals, and audit records with our team.

Book a demo

Choose which optional purposes this browser allows. Cookies that keep the site working, keep you signed in and remember this choice are always on, as is the referral cookie a referral link sets for up to 90 days. Your choice is stored in a first-party cookie for 180 days. Saving a choice that turns analytics off reloads this page if analytics was running on it. Read the privacy notice.