Get event counts over time periods. Useful for analyzing event volume trends and identifying patterns in user activity over time.
AI agents call aggregate_event_counts 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.
The tool purely retrieves and aggregates analytics data from Mixpanel (event counts and trends). It has no side effects, cannot modify data, trigger external actions, or cause financial impact. Even if misused by an AI agent, the worst outcome is excessive API queries or exposure of analytics metadata, not data loss or operational harm. This is a low-severity Read operation.
From the tool's definition Tool description states 'Get event counts over time periods' and 'analyzing event volume trends' — this is a read-only query operation that retrieves and aggregates existing event data without modifying, deleting, or executing operations.
Attacks that exploit this kind of access
Get event counts over time periods. Useful for analyzing event volume trends and identifying patterns in user activity over time. 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 aggregate_event_counts: 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.
aggregate_event_counts 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 aggregate_event_counts 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 aggregate_event_counts. 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.
aggregate_event_counts 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 →