AI agents call mixpanel_get_events to retrieve information from UnClick without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
type | string | — | Aggregation type (default: general) |
unit | string | — | Time unit (default: day) |
event | array | — | Event names to filter by |
to_date | string | — | End date (YYYY-MM-DD, default: today) |
from_date | string | — | Start date (YYYY-MM-DD, default: 7 days ago) |
project_id | string | Yes | Mixpanel project ID |
service_account_secret | string | Yes | Mixpanel Service Account secret |
service_account_username | string | Yes | Mixpanel Service Account username |
Parameters from the server's own tool schema.
This tool retrieves analytics event data from Mixpanel for a specified date range. It performs a query operation without side effects. However, severity is medium rather than low because analytics data can be sensitive (revealing business metrics, user behavior patterns, or operational intelligence); an agent with unconstrained access could extract valuable proprietary information.
From the tool's definition Tool name contains 'get' and description states 'Get Mixpanel event analytics data' — a retrieval operation with no modification or deletion.
Attacks that exploit this kind of access
Get Mixpanel event analytics data for a date range. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
mixpanel_get_events accepts 8 parameters: type, unit, event, to_date, from_date, project_id, service_account_secret, service_account_username. Required: project_id, service_account_secret, service_account_username. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for mixpanel_get_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 UnClick. Nothing to install.
mixpanel_get_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_get_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_get_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_get_events is provided by the UnClick MCP server (@unclick/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 →