tracking.funnels_run · MCP Fullstack MCP: Risk & Policy

WHAT IT DOES

What tracking.funnels_run does on MCP Fullstack

AI agents invoke tracking.funnels_run to trigger actions in MCP Fullstack. 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 tracking.funnels_run needs a policy

This tool executes analytics operations (funnel analysis) which can have side effects depending on what data is queried, how results are cached, or what downstream actions are triggered. While not destructive or directly financial, it performs active computations on tracked user/business data, making it an Execute category risk.

From the tool's definition Tool name 'tracking.funnels_run' and description 'Run funnel analysis' indicate execution of a data analysis operation. The verb 'run' combined with 'funnels_run' suggests active execution of an analytics query or pipeline, not mere data retrieval.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

tracking.funnels_run Rate-limited

tracking.funnels_run 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": {
    "tracking.funnels_run": {
      "limits": [
        {
          "counter": "tracking.funnels_run_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 MCP Fullstack, so you can run agents against it safely.

FAQ

Questions about tracking.funnels_run

What does the tracking.funnels_run tool do? +

Run funnel analysis. It is categorised as a Execute tool in the MCP Fullstack MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on tracking.funnels_run? +

Register the MCP Fullstack MCP server in PolicyLayer and add a rule for tracking.funnels_run: 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 MCP Fullstack. Nothing to install.

What risk level is tracking.funnels_run? +

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

Can I rate-limit tracking.funnels_run? +

Yes. Add a rate_limit block to the tracking.funnels_run 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 tracking.funnels_run completely? +

Set action: deny in the PolicyLayer policy for tracking.funnels_run. 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 tracking.funnels_run? +

tracking.funnels_run is provided by the MCP Fullstack MCP server (jacobfv/mcp-fullstack). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.