AI agents call meshes_list_events 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 event data with pagination support. It performs a straightforward data retrieval operation with no ability to modify, delete, or execute external actions. The blast radius of misuse is limited to potential exposure of event information that may already be accessible within the organization.
From the tool's definition Tool name is 'meshes_list_events' and description states 'List events across the organization with pagination' — core read operations with no modification or side effects.
Attacks that exploit this kind of access
List events across the organization with pagination. 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_events: 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_events 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_events 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_events. 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_events 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 →