turbo · Python MCP: Risk & Policy

WHAT IT DOES

What turbo does on Python

AI agents invoke turbo to trigger actions in Python. 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 turbo needs a policy

The tool executes Turborepo build/task pipeline commands across packages. 'Runs' indicates active execution of arbitrary tasks (build, test, lint, deploy, etc.) depending on arguments, which could have wide-ranging side effects. This maps to Execute category with high severity due to the broad blast radius of running pipeline tasks across multiple packages.

From the tool's definition Runs Turborepo tasks and returns structured per-package results

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

turbo Rate-limited

turbo 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": {
    "turbo": {
      "limits": [
        {
          "counter": "turbo_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 Python, so you can run agents against it safely.

FAQ

Questions about turbo

What does the turbo tool do? +

Runs Turborepo tasks and returns structured per-package results with cache hit/miss info. It is categorised as a Execute tool in the Python MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on turbo? +

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

What risk level is turbo? +

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

Can I rate-limit turbo? +

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

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

turbo is provided by the Python MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

turbo is one line of Python's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →