AI agents call meshes_list_rules to retrieve information from Mesheshq without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries routing rules configuration data without modifying, deleting, or executing any operations. It is a straightforward read operation that returns existing rule metadata. The filtering options confirm it is a query/list utility. Severity is low because while the data retrieved may be sensitive to system architecture, the tool itself performs no state changes or dangerous operations.
From the tool's definition Tool name contains 'list' and description states 'List all routing rules' with support for filtering—pure data retrieval with no side effects.
Attacks that exploit this kind of access
List all routing rules across the organization. Rules bind event types to connections with action metadata. Supports filtering by event, resource, and resource_id. It is categorised as a Read tool in the Mesheshq MCP Server, which means it retrieves data without modifying state.
Register the Mesheshq MCP server in PolicyLayer and add a rule for meshes_list_rules: 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_list_rules 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 meshes_list_rules 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_list_rules. 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_list_rules 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 →