AI agents use mixpanel_track_event to create or update resources in UnClick — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
event | string | Yes | Event name |
token | string | Yes | Mixpanel project token (for ingestion) |
project_id | string | Yes | Mixpanel project ID |
properties | object | — | Additional event properties |
distinct_id | string | — | User distinct ID (default: anonymous) |
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 sends/writes event data to Mixpanel analytics. It creates new records in the analytics system. While not destructive or financial, it modifies external state by writing tracking data, and misuse could pollute analytics data or be used for tracking manipulation.
From the tool's definition Track a custom event in Mixpanel
Risk signalsHandles credentials or secrets (token)
Attacks that exploit this kind of access
Track a custom event in Mixpanel. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
mixpanel_track_event accepts 7 parameters: event, token, project_id, properties, distinct_id, service_account_secret, service_account_username. Required: event, token, 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_track_event: 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_track_event is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the mixpanel_track_event 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_track_event. 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_track_event 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 →