Govern AI agents on MCP Bridge
Add governance to MCP tool calls via a bridge that sits between MCP clients and servers. The MCP Bridge pack evaluates every tool invocation against policy before forwarding to the target server.
What this pack does
- Pre-dispatch policy evaluation on MCP tool calls
- Gateway-level approval gates
- Output safety checks on tool responses
- Protocol-native audit trail
Use cases
Govern all MCP tool calls from Claude, Cursor, or custom clients
Require approval for file system and database MCP tools
Audit every MCP interaction across your organization
Quick setup
- 1Install the MCP Bridge pack: cordumctl pack install mcp-bridge
- 2Configure upstream MCP server endpoints
- 3Define tool-level governance policies
- 4Point your MCP clients to the Cordum bridge endpoint
Frequently asked questions
How does Cordum govern MCP Bridge actions?
Cordum evaluates every MCP Bridge action against your policy before execution. The Safety Kernel returns Allow, Deny, or Require Approval decisions, ensuring agents operate within approved boundaries.
Do I need to modify my existing MCP Bridge setup?
No. The Cordum MCP Bridge pack installs as an overlay. It intercepts agent actions at the governance layer without changing your existing MCP Bridge configuration.
What happens if an agent action is denied?
The action is blocked before execution, logged in the audit trail, and optionally triggers an alert. The agent receives a structured denial with the policy reason, so it can adjust its approach.
Ready to govern MCP Bridge?
Other integrations
Approval notifications and agent alerts in Slack channels.
Govern AI agent actions on GitHub repositories.
Govern AI agent actions across AWS services.
Governance for AI agents managing Jira workflows.
Govern AI agents responding to Kubernetes incidents.
Feed Datadog alerts into governed agent workflows.