mesh_inbox

THE RISK

Low Risk

Why mesh_inbox needs a policy

The tool reads/fetches incoming messages from a mailbox-style inbox. It is a polling/read operation with no write, execute, or destructive capabilities described. Severity is low as misuse would only expose message contents, not modify or destroy data.

From the tool's definition "Check your incoming messages from other agents" and "Call periodically to stay in sync" — purely retrieves/queries data with no side effects mentioned.

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

POLICY

How to control mesh_inbox

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_inbox:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "mesh_inbox": {}
  }
}

mesh_inbox is read-only, so it stays allowed — but 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.

CAP 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_send Send a message to another agent on the mesh. Use peer ID from mesh_peers, or 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_peers Discover other AI agents connected to the SLM Mesh network. Returns active peers with thei

All 8 Slm Mesh tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about mesh_inbox

What does the mesh_inbox tool do? +

Check your incoming messages from other agents. Call periodically to stay in sync with your peers. It is categorised as a Read tool in the Slm Mesh MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on mesh_inbox? +

Register the Slm Mesh MCP server in PolicyLayer and add a rule for mesh_inbox: 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_inbox? +

mesh_inbox is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit mesh_inbox? +

Yes. Add a rate_limit block to the mesh_inbox 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_inbox completely? +

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

mesh_inbox 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 →