mesh_send

THE RISK

Medium Risk

Why mesh_send needs a policy

This tool creates new messages that are sent and presumably stored in the mesh inbox system (evidenced by sibling tool mesh_inbox). While message transmission itself is reversible (messages can be deleted or ignored), the act of sending constitutes creation of new data on the network.

From the tool's definition Send a message to another agent on the mesh. Use peer ID from mesh_peers, or [description cuts off]. The tool creates/transmits new messages in a peer-to-peer network, modifying the state of the mesh communication system.

Documented attack patterns abuse exactly the kind of access mesh_send gives an agent:

POLICY

How to control mesh_send

PolicyLayer is an MCP gateway — it sits between your AI agents and Slm Mesh, and nothing reaches the server without passing your rules. This is the rule we recommend for mesh_send:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "mesh_send": {
      "limits": [
        {
          "counter": "mesh_send_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

mesh_send stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

Create a free account and register Slm Mesh — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Slm Mesh tools

Execute mesh_lock Acquire, release, or query distributed file locks. ALWAYS query before editing shared file Write mesh_state Read or write shared state across agent sessions. Use for sharing config values, API endpo Write mesh_summary Set a summary of what you are currently working on. This is visible to other agents on the Read mesh_events Read, subscribe to, or unsubscribe from mesh events. Events include peer joins/leaves, fil Read mesh_status Check the health and status of the SLM Mesh broker. Shows peer counts, message stats, lock Read mesh_inbox Check your incoming messages from other agents. Call periodically to stay in sync with you Read mesh_peers Discover other AI agents connected to the SLM Mesh network. Returns active peers with thei

All 8 Slm Mesh tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about mesh_send

What does the mesh_send tool do? +

Send a message to another agent on the mesh. Use peer ID from mesh_peers, or. It is categorised as a Write tool in the Slm Mesh MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on mesh_send? +

Register the Slm Mesh MCP server in PolicyLayer and add a rule for mesh_send: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Slm Mesh. Nothing to install.

What risk level is mesh_send? +

mesh_send is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit mesh_send? +

Yes. Add a rate_limit block to the mesh_send rule in your PolicyLayer 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 mesh_send completely? +

Set action: deny in the PolicyLayer policy for mesh_send. 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 mesh_send? +

mesh_send is provided by the Slm Mesh MCP server (qualixar/slm-mesh). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Slm Mesh tool call.

Start from Slm Mesh, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →