Get a list of the most common events over the last 31 days. Useful for identifying key user actions, prioritizing feature development, and understanding overall platform usage patterns.
AI agents call get_top_events to retrieve information from Mixpanel MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and aggregates historical analytics data (event counts over 31 days) from Mixpanel. It performs no modifications, deletions, code execution, or financial operations.
From the tool's definition Tool name 'get_top_events' and description 'Get a list of the most common events' — uses read-only query operation to retrieve historical event data without modification or execution.
Attacks that exploit this kind of access
Get a list of the most common events over the last 31 days. Useful for identifying key user actions, prioritizing feature development, and understanding overall platform usage patterns. It is categorised as a Read tool in the Mixpanel MCP MCP Server, which means it retrieves data without modifying state.
Register the Mixpanel MCP server in PolicyLayer and add a rule for get_top_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 Mixpanel MCP. Nothing to install.
get_top_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 get_top_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 get_top_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.
get_top_events is provided by the Mixpanel MCP server (mendeel/mixpanel-mcp). 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 →