MCP servers · csoai-org

Agent Policy Enforcement MCP

MCP server that defines per-agent-pair access policies for agent-to-agent (A2A) calls, such as limiting which agent may call which service and under what conditions.

This text was machine-translated from the publisher's own information and has not been checked by a human editor. The publisher's original text is the reference.

This resource was imported automatically from the sources listed below and has not been reviewed by the AI Gate team yet. The description is the publisher's own, as published. Check the repository before installing.

The publisher marked this resource as deprecated. Prefer the alternatives below.

What it does

Provides per-agent-pair identity and access management for A2A communication. Policies are written as conditions on a pair of agents, for example allowing an orchestrator agent to call a billing agent only when the amount is below 100. The server exposes tools to define a policy, evaluate a call against policies, and list existing policies.

It suits teams running several agents that call one another and need to restrict which agent can invoke which, and under what conditions. It is one of five MCP servers in the MEOK A2A pack (with prompt injection firewall, data residency, certified handoff, audit logger and rate limiter), and it can also be installed on its own.

Running it means adding the server to an MCP client configuration, such as claude_desktop_config.json for Claude Desktop, or installing the package with pip and launching the agent-policy-enforcement-mcp command over stdio transport. Self-hosting is listed under the MIT licence. Paid tiers are offered by the publisher and add HMAC-signed attestations.

Limitations and requirements

Requires an MCP client configured to launch the server over stdio, or a pip installation of the package. Hosted tiers beyond self-hosting are paid and add attestations verifiable through the publisher's service.

Safety

Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.

  • Runs code or changes an assistant's behaviour

Sources

  • Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
    io.github.CSOAI-ORG/agent-policy-enforcement-mcp

    Per-agent-pair IAM for A2A. Define policies ('orchestrator may call billing only when amount<100...

    v1.0.11
    As shown on registry.modelcontextprotocol.io when we last read it
MCP servers
hashicorp

Terraform MCP Server (HashiCorp)

HashiCorp's MCP server that gives an assistant current Terraform Registry information on providers, modules and policies, and can manage HCP Terraform workspaces.

1.6K GitHub starsCloud & DevOpsSoftware development
Updated 17 Nov 2026
MCP servers
modelcontextprotocol

MCP reference servers

Seven small example servers maintained by the Model Context Protocol project: files, Git, web fetching, memory, time, step-by-step thinking and a test server.

92K GitHub starsSoftware development
Updated 18 Nov 2026
MCP servers
redis

Redis MCP Server

Redis's official MCP server that lets an AI assistant store, read and search data in a Redis database, including streams, JSON documents and vector indexes.

642 GitHub starsData & databasesSoftware development
Updated 17 Nov 2026
MCP servers
firecrawl

Firecrawl MCP Server (web search and scraping)

Firecrawl's MCP server that lets an AI assistant search the web, turn pages and PDFs into clean Markdown, crawl sites and interact with dynamic pages.

7.8K GitHub starsWeb, search & browserProductivity & automation
Updated 17 Nov 2026