Compare

Open-source MCP gateways and agent governance tools compared

Six open-source projects that control what an AI agent may do with its tools, compared feature by feature.

Three places to stop a tool call

An agent uses tools in two ways. It runs commands on its own machine, and it calls MCP servers over the network. A check can sit in three places.

Developer machine
AI agentClaude Code, Codex, or one you wrote
1
Library inside the agentchecks tool calls in code you write
checks hereStrazaMicrosoft AGT
runs a command
2
Hook before each commandchecks shell commands and file writes
checks hereStrazaMicrosoft AGTObot
Shell and files

Whoever controls this machine can switch checks 1 and 2 off.

calls an MCP tool
Your servers
3
MCP gatewaychecks every MCP call and keeps the credentials
checks hereStrazaObotagentgatewayIBM ContextForgeDocker MCP Gateway
MCP serversGitHubDatabaseSlack

The agent has no other way to these servers, so it cannot skip check 3.

Feature comparison

YesPartialNo not in the open-source projectClick a row to highlight it.

StrazaObotagentgatewayIBM ContextForgeDocker MCP GatewayMicrosoft AGT
MCP gatewayYesPart of the Straza serverYesAlso hosts MCP serversYesAlso A2A, LLM and HTTP trafficYesAlso wraps REST and gRPC as toolsYesLocal, one per developerPartialA library class, and a proxy that wraps one server
Delegated admin of one MCP serverYesEach server has its own admin role, assigned by your IGAPartialA Power User+ manages the servers they publishPartialRules you write on the admin API. No rolesPartialOne owner per gateway, transferable. Roles are team-wideNoLocal, one user, no rolesNoNo server registry. Set up in code
Agent drafts a change, a person publishes itYesNeeds the drafting role. Straza checks each draftPartialAn agent’s API key acts with its user’s role, at onceNoConfig API applies at once. Nothing for agentsNoAPI applies at once. Approvals only for sign-upsPartialAgent tools change servers at once. No publish stepPartialAgent tools create policy at once. No publish step
Hooks for coding agentsYesClaude Code, Codex CLI, Gemini CLI. Decides each commandPartialAllows or blocks a whole tool by name. ExperimentalNoNetwork traffic onlyNoGateway traffic onlyNoMCP onlyYesClaude Code, Copilot CLI, OpenCode, Antigravity
SDK for agents you writeYesPython kit for LangChain, OpenAI Agents SDK and Claude Agent SDKNoGateway and device agentNoNetwork proxyNoGateway onlyNoGateway onlyYesPython, TypeScript, .NET, Rust and Go
LLM guardrailsNoDecides actions, not textYesLLM gateway with guardrailsYesLLM routing with guardrailsPartialPlugins on tool traffic, such as PII filtersNoScans tool arguments for secretsYesInspects and rewrites prompts and outputs
Human approval of a callYesPhone app, console, browser or Slack. The phone signs itNoAdmins approve servers, not single callsNoCan call an external decision serviceNoPasses the server's own prompt to the same userNoPaid edition prompts the person running the agentPartialHandlers you wire up. No approver interface
RBACYesRoles per MCP server, assigned to people and agentsYesPlatform roles and access policies for users and groupsPartialRules on token claims. No role storeYesTeams with built-in and custom rolesNoNo users or roles in open sourcePartialPolicy rules per agent and trust score
Access to one repository or databaseYesA role can name the objects it coversPartialA condition you write on the call's argumentsPartialCEL you write per toolPartialThrough the OPA or Cedar pluginNoPartialRego or Cedar rules you write on tool arguments
SCIM integrationYesPeople, agents and each agent's sponsor, from your IGAPartialPeople only, from Okta, Entra and OneLoginNoReads claims from your identity provider's tokensNoSingle sign-on. Its docs say the user API is not SCIMNoLocal tool, no usersNoHas an adapter for Entra Agent ID
Credentials stay off the agentYesThe gateway adds them to an allowed callYesStores and refreshes upstream OAuth tokensPartialStatic keys and token exchange. Per-user vault is paidYesPer gateway and per userYesSecrets scoped to each serverNoListed as out of scope
Signed policyYesEd25519, checked by every clientNoNoNoPartialSigns MCP server images, not policyNoSigned bundles are a proposed design
Tamper-evident auditYesSHA-256 hash chain, verified from the CLINoLogs with export. Payloads only for an Auditor roleNoAccess logs and OpenTelemetryNoListed as under evaluation. Audit is off by defaultNoLogs tool names, not argumentsYesSHA-256 hash chain in a file beside the agent
No matching ruleDenied, for an MCP tool no role reachesDenied without a grantAllowed with no rules. Denied once allow rules existDeniedAllowed, for any enabled toolAllowed with no policy loaded
LicenseAGPL-3.0-only core. Kits and phone app Apache-2.0MIT. A license key lifts the 100-user limitApache-2.0. Paid Solo Enterprise editionApache-2.0MIT. Policy engine is in Docker Desktop, closedMIT

Which one for which job

You needStart with
One policy for coding agents, Python agents you write and MCP serversStraza
A person approves risky calls on a phoneStraza
Agents managed in your IGA like peopleStraza
One console for MCP servers, LLM access and skillsObot
MCP, LLM and API traffic through one proxy on Kubernetesagentgateway
Existing REST and gRPC services offered as MCP toolsIBM ContextForge
Each MCP server in its own container on a laptopDocker MCP Gateway
Checks on prompts and outputs inside an agent you writeMicrosoft AGT

Sources

  • Every cell comes from the project's own repository or docs, read on November 13, 2026. The rows on delegated administration and on agent drafting were read on November 17, 2026.
  • "No" means the project says so, or a search of its open-source repository and docs found nothing. It says nothing about a paid edition.
  • Straza publishes this page. Check the rows that matter to you against each project's repository, linked in the table above.
  • Not in the table: Preloop, a smaller project with human approval on a phone or in Slack, and Bifrost, an LLM gateway first.

Found a wrong cell? Write to hello@straza.ai or open an issue on Strazahq/straza. Product names belong to their owners. Straza is not affiliated with any of them.