AI agents call mixpanel_get_retention 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 |
|---|---|---|---|
unit | string | — | Time unit (default: day) |
event | string | — | Retention event to measure |
to_date | string | — | End date (YYYY-MM-DD) |
from_date | string | — | Start date (YYYY-MM-DD, default: 30 days ago) |
born_event | string | — | Event that defines user acquisition |
project_id | string | Yes | Mixpanel project ID |
retention_type | string | — | Retention type (default: birth) |
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 and queries existing user retention analytics from Mixpanel. It performs no data creation, modification, deletion, or external execution. While it accesses potentially business-sensitive analytics data, misuse would result in unauthorized information disclosure rather than operational impact. This is a standard Read category operation with low severity.
From the tool's definition Tool name and description indicate retrieval of analytics data: 'Get user retention analytics from Mixpanel' - the verb 'Get' and nature of 'retention analytics' (historical/computed metrics) indicate a read-only query operation with no data modification or…
Attacks that exploit this kind of access
Get user retention analytics from Mixpanel. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
mixpanel_get_retention accepts 9 parameters: unit, event, to_date, from_date, born_event, project_id, retention_type, 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_retention: 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_retention 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_retention 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_retention. 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_retention 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 →