AI agents call meshes_get_event 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 queries and returns event information (delivery status, rule_events metadata). It performs no mutations, deletions, or external operations—purely a read operation. Even in the context of an integration layer, retrieving event details has minimal blast radius if misused by an AI agent, as it only exposes existing data structures without triggering external changes.
From the tool's definition Tool name 'meshes_get_event' and description 'Get event details' indicate data retrieval. The description explicitly states it retrieves event details, delivery status, and rule results without mentioning any mutations, deletions, or side effects.
Attacks that exploit this kind of access
Get event details including delivery status and per-rule results (rule_events). Each rule_event shows connection, integration_type, status, attempt_count, and last_error. 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_get_event: 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_get_event 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_get_event 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_get_event. 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_get_event 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 →