Delete a routing rule. Events matching this rule will no longer be routed to its connection.
AI agents call meshes_delete_rule to permanently remove resources in Mesheshq — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool performs an irreversible deletion of a routing rule. While the deletion itself does not destroy data, it permanently removes configuration that governs event routing behavior in the Meshes integration layer. This is a destructive action that cannot be undone without recreating the rule, making it more severe than a reversible Write action.
From the tool's definition Tool name includes 'delete'; description states 'Delete a routing rule' which irreversibly removes a rule configuration.
Attacks that exploit this kind of access
Delete a routing rule. Events matching this rule will no longer be routed to its connection. It is categorised as a Destructive tool in the Mesheshq MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mesheshq MCP server in PolicyLayer and add a rule for meshes_delete_rule: 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 Mesheshq. Nothing to install.
meshes_delete_rule is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the meshes_delete_rule 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 meshes_delete_rule. 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.
meshes_delete_rule is provided by the Mesheshq MCP server (mesheshq/meshes-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →