Get the sum of a numeric event property over time. Useful for tracking totals like revenue.
AI agents call segmentation_sum 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.
The tool queries and aggregates existing analytics data (sum of numeric properties), returning computed results without side effects. While it may report on revenue-related metrics, it does not move money, modify data, execute code, or perform destructive operations. This is a standard analytics read operation.
From the tool's definition Tool description states 'Get the sum of a numeric event property over time' — this is a retrieval/aggregation operation. The example use case 'tracking totals like revenue' is a query, not a financial transaction.
Attacks that exploit this kind of access
Get the sum of a numeric event property over time. Useful for tracking totals like revenue. It is categorised as a Read tool in the Mixpanel MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Mixpanel MCP Server MCP server in PolicyLayer and add a rule for segmentation_sum: 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.
segmentation_sum 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 segmentation_sum 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 segmentation_sum. 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.
segmentation_sum 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.
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 →