mixpanel_query_events
AI agents call mixpanel_query_events to retrieve information from Integrations MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name 'mixpanel_query_events' strongly suggests querying/retrieving event data from Mixpanel analytics. Query operations are inherently read-only and retrieve data without side effects. Severity is medium rather than low because querying analytics events could expose sensitive behavioral or user data, and the empty description reduces confidence slightly.
From the tool's definition Tool name contains 'query_events' which indicates data retrieval. The 'query' verb and 'events' object suggest reading event data from Mixpanel without modification.
Attacks that exploit this kind of access
mixpanel_query_events. It is categorised as a Read tool in the Integrations MCP MCP Server, which means it retrieves data without modifying state.
Register the Integrations MCP server in PolicyLayer and add a rule for mixpanel_query_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 Integrations MCP. Nothing to install.
mixpanel_query_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 mixpanel_query_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 mixpanel_query_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.
mixpanel_query_events is provided by the Integrations MCP server (shriram-vasudevan/integrations-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 →