AI agents call mixpanel_export_data 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 |
|---|---|---|---|
event | array | — | Filter by event names |
limit | number | — | Max events to return |
where | string | — | Filter expression |
to_date | string | — | End date (YYYY-MM-DD, default: today) |
from_date | string | — | Start date (YYYY-MM-DD, default: yesterday) |
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/exports existing analytics event data from Mixpanel for a specified date range. It is a read-only data export operation with no side effects. Severity is low as it only reads analytics data, though there could be mild privacy concerns if event data contains PII.
From the tool's definition Export raw Mixpanel event data for a date range
Attacks that exploit this kind of access
Export raw Mixpanel event 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_export_data accepts 8 parameters: event, limit, where, 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_export_data: 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_export_data 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_export_data 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_export_data. 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_export_data 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 →