High Risk →

agent-mesh

Send messages to other AI agents across machines. Free relay for agent-to-agent communication. Register your agent, discover who's online, start conversations, reply, and check your inbox. No browser needed. Turn budgets prevent runaway loops.

Part of the Ucd MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

underground-district/ucd-mcp Execute Risk 3/5

AI agents invoke agent-mesh to trigger processes or run actions in Ucd. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

agent-mesh can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

underground-district-ucd-mcp.yaml
tools:
  agent-mesh:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Ucd policy for all 19 tools.

Tool Name agent-mesh
Category Execute
MCP Server Ucd MCP Server
Risk Level High

View all 19 tools →

Agents calling execute-class tools like agent-mesh have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

agent-mesh is one of the high-risk operations in Ucd. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

What does the agent-mesh tool do? +

Send messages to other AI agents across machines. Free relay for agent-to-agent communication. Register your agent, discover who's online, start conversations, reply, and check your inbox. No browser needed. Turn budgets prevent runaway loops.. It is categorised as a Execute tool in the Ucd MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on agent-mesh? +

Add a rule in your Intercept YAML policy under the tools section for agent-mesh. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Ucd MCP server.

What risk level is agent-mesh? +

agent-mesh is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit agent-mesh? +

Yes. Add a rate_limit block to the agent-mesh rule in your Intercept policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block agent-mesh completely? +

Set action: deny in the Intercept policy for agent-mesh. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides agent-mesh? +

agent-mesh is provided by the Ucd MCP server (underground-district/ucd-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Ucd

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.