run_jql · Mixpanel MCP Server MCP: Risk & Policy

WHAT IT DOES

What run_jql does on Mixpanel MCP Server

AI agents invoke run_jql to trigger actions in Mixpanel MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why run_jql needs a policy

JQL execution represents arbitrary code execution against a production analytics database. An AI agent could craft queries that: extract sensitive user data at scale, manipulate analytics results, cause denial-of-service through expensive queries, or exfiltrate proprietary business intelligence.

From the tool's definition Tool allows running arbitrary JQL (JavaScript Query Language) scripts against Mixpanel data with no apparent restrictions or sandboxing mentioned. The description explicitly states it 'Allows complex custom queries' without limiting query scope.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_jql Rate-limited

run_jql stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_jql": {
      "limits": [
        {
          "counter": "run_jql_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Mixpanel MCP Server, so you can run agents against it safely.

FAQ

Questions about run_jql

What does the run_jql tool do? +

Run a JQL (JavaScript Query Language) script against Mixpanel data. Allows complex custom queries. It is categorised as a Execute tool in the Mixpanel MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_jql? +

Register the Mixpanel MCP Server MCP server in PolicyLayer and add a rule for run_jql: 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.

What risk level is run_jql? +

run_jql is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run_jql? +

Yes. Add a rate_limit block to the run_jql 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.

How do I block run_jql completely? +

Set action: deny in the PolicyLayer policy for run_jql. 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.

What MCP server provides run_jql? +

run_jql 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.