19 tools. 2 can modify or destroy data without limits.
2 write tools that can modify data. Rate limits recommended.
Last updated:
Write operations (aggregate_event_counts) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.
Execute tools (custom_jql) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.
aggregate_event_counts:
rules:
- rate_limit: 30/hour Prevents bulk unintended modifications from agents caught in loops.
aggregated_event_property_values:
rules:
- rate_limit: 60/minute Controls API costs and prevents retry loops from exhausting upstream rate limits.
The Mixpanel Integration server has 1 write tools including aggregate_event_counts. Set rate limits in your policy file -- for example, rate_limit: 10/hour prevents an agent from making more than 10 modifications per hour. Intercept enforces this at the transport layer.
19 tools across 3 categories: Execute, Read, Write. 17 are read-only. 2 can modify, create, or delete data.
One line change. Instead of running the Mixpanel Integration server directly, prefix it with Intercept: intercept -c dragonkhoi-mixpanel-mcp.yaml -- npx -y @dragonkhoi/mixpanel-mcp. Download a pre-built policy from policylayer.com/policies/dragonkhoi-mixpanel-mcp and adjust the limits to match your use case.
Starter policies available for each. Same risk classification, same one-command setup.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.