turbo

Runs Turborepo tasks and returns structured per-package results with cache hit/miss info.

SERVERGithub SOURCE@paretools/github

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dave-london-github/turbo.md

WHAT IT DOES

What turbo does on Github

AI agents invoke turbo to trigger actions in Github. 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.

RISK

Why turbo is rated High

This tool executes arbitrary Turborepo tasks (which can include build scripts, test runners, deployment pipelines, etc.) across multiple packages. The blast radius is high because a misconfigured or malicious task could run destructive scripts, exfiltrate data, or trigger deployments.

From the tool's definition 'Runs Turborepo tasks' — actively executes build/test/lint tasks across packages in a monorepo

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs turbo safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Github, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For turbo, this is the rule to start with:

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.

The button opens the PolicyLayer dashboard: create your workspace, connect Github, apply this rule, and every turbo call is checked against it from then on.

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 Github 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 Github 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 Github. 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 Github MCP server (@paretools/github). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Github, and thousands of servers like it.

This server

All 202 Github tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →