AI agents call meshes_get_workspace_event_types 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 retrieves event type configuration for a workspace. It performs a read-only operation that fetches metadata about configured events. There is no data modification, deletion, execution of external operations, or financial impact. The blast radius of misuse is minimal—an agent could enumerate event types but cannot modify, delete, or trigger them.
From the tool's definition Tool name indicates 'get' operation; description states 'List the event types' which retrieves configuration data without modification or side effects.
Attacks that exploit this kind of access
List the event types configured for a workspace, including each key, label, description, and active state. 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_workspace_event_types: 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_workspace_event_types 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_workspace_event_types 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_workspace_event_types. 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_workspace_event_types 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 →