AI agents use meshes_create_rule to create or update resources in Mesheshq — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mesheshq environment.
This tool creates routing rules that establish bindings between events and connections. While it creates configuration data (reversible via meshes_delete_rule), the act of creating rules that route events to destinations could have downstream effects on integration behavior and data flow.
From the tool's definition Tool name is 'meshes_create_rule' and description states 'Create a routing rule that binds an event type to a connection.' The verb 'Create' and the action of binding configuration indicates data creation/modification.
Attacks that exploit this kind of access
Create a routing rule that binds an event type to a connection. The metadata.action field is required and determines what the destination does (e.g.,. It is categorised as a Write tool in the Mesheshq MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mesheshq MCP server in PolicyLayer and add a rule for meshes_create_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_create_rule is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the meshes_create_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_create_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_create_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 →