durin
Book A Demo
Knowledge base
Policies & approvals

Understanding policy decisions

Understand how Durin checks access and returns allowed, denied or approval-required decisions, separately from provider execution outcomes.

Everyone1 min read

Required checks come first

Every request must pass current identity, membership, connection, team, credential, reviewed tool, resource, and inspection checks. A configurable allow setting cannot override a failed check. Team restrictions can narrow organization policy.

The three decisions

The decision describes authorization, not provider success.

  • Allowed: the request may proceed; inspect execution separately.
  • Denied: the request does not execute. Read the reason before changing settings.
  • Approval-required: the action has not executed. An approver your approval workflow names, or another active administrator, must review it, then the requester retries the exact call before expiry.

Frequently asked questions

Are reads always allowed?

No. Default deny can block reads and writes. Reviewed reads under default allow still need all mandatory checks.

Do production and sandbox use different write rules?

Workspace presets apply to both. Custom rules can add stricter conditions for a specific environment, such as approval for production writes. Production still requires reviewed tools and current provider authorization.

Try Durin with your MCP workflow.

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.