durin
Book A Demo

MCP Governance vs API gateway: which controls do you need?

Compare MCP Governance with API gateway controls, check what your existing platform supports, and identify gaps in tool policy, approvals, and audit.

The decision in brief

API gateways can provide some MCP Governance controls. Keep existing API protection, verify your platform’s MCP support, and add the missing controls for tool access, approvals, and execution evidence. These requirements do not necessarily require separate deployments.

Start with the capabilities

An API gateway commonly routes requests and applies authentication, rate limits, and other policies before traffic reaches a service. MCP Governance adds requirements for tool access, approvals, and evidence across MCP connections and requests. One platform may provide both sets of controls.

For example, Azure API Management can expose existing MCP servers or turn managed REST operations into MCP tools, with gateway policies for access and traffic management.

The design question is which requirements your configured deployment satisfies. Supporting MCP transport does not by itself prove exact human approvals, tool-change review, or safe handling of uncertain writes.

MCP support in Azure API Management

Compare these controls

Use the same checklist for a dedicated MCP product and an API gateway with MCP support. Test each requirement on a working deployment.

  • Transport: confirm the MCP transport and session behavior used by your clients, including streaming and timeouts.
  • Discovery: check which tools a requester can see and how changed tool definitions are reviewed.
  • Authorization: test tool, connection, credential, and resource restrictions as well as HTTP authentication.
  • Approvals: verify who can approve, what the grant binds, when it expires, and how it is consumed.
  • Execution: distinguish an authorization decision from a provider result, especially after a write timeout.
  • Evidence: trace the requester, connection, tool, decision, approval where required, and outcome without exposing secrets.

HTTP routing and tool authorization

MCP tool calls carry a method, tool name, and arguments inside protocol messages. Multiple tools may share one HTTP endpoint. A rule that only permits that endpoint cannot distinguish a document search from a record deletion.

An MCP-aware policy or integration can inspect the relevant operation. Evaluate that implementation directly: route filters, token validation, and MCP-aware tool controls solve different parts of the request.

A refund tool makes the distinction concrete. Permission to reach the service does not answer whether this requester may refund this order, for this amount, using this account. Those conditions need enforcement somewhere on the path.

MCP security best practices

Identity and provider authority

An identity provider establishes identity and can supply groups, app assignments, and other authorization inputs. A gateway and the upstream service must use the relevant inputs to decide whether the requested action is permitted.

Check both sides of the connection: how the client authenticates to the gateway and how the gateway authenticates upstream. A gateway approval cannot grant permissions that the upstream credential lacks. Direct access using another credential remains outside that gateway’s coverage.

Test the approval lifecycle

A confirmation in an agent client, an approved change ticket, and an exact server-enforced approval are different controls. Decide which you need and test the full lifecycle, including changed arguments, revoked membership, expiry, and repeated requests.

In Durin, an approver an approval workflow names, or another active administrator, approves a request bound to its authorization context and argument digest. The requester retries the exact call before expiry. Approval does not automatically execute it, and an uncertain dispatched write is not automatically repeated.

An API request log can help diagnose the HTTP exchange. Also check whether your records identify the policy decision and execution outcome; a successful HTTP response alone does not establish a successful tool action.

Review an exact approval in Durin

Buyer options and evidence to request

Documentation research: October 3, 2026. Compare the same identity, resource, approval and failure tests on your selected versions before choosing.

Cloudflare MCP server portals provide a central entry point to configured MCP servers using Cloudflare Access. Their documentation lists portal-specific policy limitations. Teams already using Cloudflare should evaluate the portal and each server’s policies together, and demonstrate any required per-action approval behavior.

Azure API Management can expose existing remote MCP servers or managed REST operations as tools. This can fit teams with an existing API management estate. Verify the selected tier, transport and policy scope, and demonstrate exact approvals and uncertain-write handling separately.

Durin fits when the evaluation requires reviewed tool mappings, independent exact approvals, and separate policy and execution records. Budget for provider setup, deployed validators and connection charges; it only governs requests routed through Durin.

A direct provider MCP connection may be sufficient when provider permissions and client confirmation meet the requirements. You own the cross-provider evidence and revocation tests. No missing capability is inferred from an omitted marketing claim.

Choose by the control you need
ApproachFits whenVerify before choosing
Direct provider MCPProvider permissions and client review meet your scopeRevocation and evidence across every client
Cloudflare MCP server portalsYou want a shared portal with Access controlsPortal and per-server policies; required action approvals
Azure API ManagementYour API estate needs remote MCP exposureTransport, tier and operation-policy scope
DurinYou need reviewed tools, exact approvals and execution recordsProvider/client compatibility, validator and activation
Cloudflare MCP server portals and limitationsAzure API Management MCP supportRun the vendor-neutral evaluation kitDurin connection pricing and Enterprise terms

Keep, extend, or add

Keep the gateway controls required by your existing APIs. If your platform already supports MCP, first test whether it meets the tool access, review, and evidence requirements above.

Extend that deployment when its supported policies can meet the requirements and your team can maintain them. Add a dedicated service when it provides controls or operating workflows you need. Account for the extra network hop, availability dependency, and ownership.

Durin provides a governed path for reviewed connections, mandatory access checks, configurable write approval, and decision and execution records. Evaluate it with one approved client and a supported sandbox connection before expanding the rollout.

Durin’s MCP request pathEvaluate a Durin connectionDurin security scope

How governance fits with your API gateway.

Does MCP Governance require replacing our API gateway?

Not simply because agents use MCP. Keep the controls your APIs depend on, then assess whether the existing gateway can meet your MCP requirements or needs a complementary service.

Can an API gateway support MCP?

Yes. Some API management platforms expose or proxy MCP servers and apply access policies. Check your product version, deployment tier, supported transport, and policy scope.

What needs more than HTTP authentication?

Tool visibility, connection and resource authorization, exact approval binding, and execution outcomes need controls that understand those concepts. Verify them independently of token validation.

Do approvals replace upstream OAuth scopes?

No. An approval authorizes an otherwise permitted request. It cannot expand the permissions held by the connection’s upstream credential.

Do MCP Governance and API gateway controls need separate deployments?

No. A single platform may implement both roles. Separation should follow the controls, ownership, and operational requirements of your system.

Test the controls your agent path needs.

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.