query_events

Query event data with segmentation. Returns time-series event counts, optionally segmented by a property.

Server Mixpanel MCP Server t-campbell18/mcp-mixpanel
Category Read
Risk class Low
Parameters 00 required

What query_events does on Mixpanel MCP Server

AI agents call query_events to retrieve information from Mixpanel MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why query_events needs a policy

This tool queries and retrieves event analytics data from Mixpanel without creating, modifying, or deleting records. It is a Read operation. Severity is medium because Mixpanel event data may contain sensitive business metrics, user behavior insights, or PII embedded in events, which could be misused if accessed by a compromised agent or in an unauthorized context.

From the tool's definition Tool name 'query_events' and description 'Query event data with segmentation. Returns time-series event counts' indicate data retrieval without modification. The verb 'query' and 'returns' confirm read-only operation.

Questions about query_events

What does the query_events tool do? +

Query event data with segmentation. Returns time-series event counts, optionally segmented by a property. It is categorised as a Read tool in the Mixpanel MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on query_events? +

Register the Mixpanel MCP Server MCP server in PolicyLayer and add a rule for 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 Mixpanel MCP Server. Nothing to install.

What risk level is query_events? +

query_events is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit query_events? +

Yes. Add a rate_limit block to the 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.

How do I block query_events completely? +

Set action: deny in the PolicyLayer policy for 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.

What MCP server provides query_events? +

query_events is provided by the Mixpanel MCP Server MCP server (t-campbell18/mcp-mixpanel). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.