Check the health and status of the SLM Mesh broker. Shows peer counts, message stats, lock counts, and uptime.
AI agents call mesh_status to retrieve information from Slm Mesh without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
mesh_status is a monitoring/diagnostic tool that retrieves and reports operational metrics about the mesh broker. It performs no writes, deletions, code execution, or financial operations. The blast radius of misuse is minimal since an agent querying broker health cannot cause harm to the system or data.
From the tool's definition Tool description states it 'Check[s] the health and status' and 'Shows peer counts, message stats, lock counts, and uptime' — all query operations with no modification or side effects.
Documented attack patterns abuse exactly the kind of access mesh_status gives an agent:
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_status:
{
"version": "1",
"default": "deny",
"tools": {
"mesh_status": {}
}
}mesh_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check the health and status of the SLM Mesh broker. Shows peer counts, message stats, lock counts, and uptime. It is categorised as a Read tool in the Slm Mesh MCP Server, which means it retrieves data without modifying state.
Register the Slm Mesh MCP server in PolicyLayer and add a rule for mesh_status: 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.
mesh_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the mesh_status 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.
Set action: deny in the PolicyLayer policy for mesh_status. 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.
mesh_status 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.
Start from Slm Mesh, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 Slm Mesh tools catalogued and risk-classified — across an index of 43,000+ MCP servers.