run_tasks

Submit independent worker tasks and wait for their results.

SERVERMcp Control Plane SOURCEalbertik322-sudo/mcp-control-plane

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/mcp-control-plane/run-tasks.md

WHAT IT DOES

What run_tasks does on Mcp Control Plane

AI agents invoke run_tasks to trigger actions in Mcp Control Plane. 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 run_tasks is rated High

This tool submits and executes tasks on remote workers, which constitutes running code or operations on external systems. The blast radius is high because task payloads could perform arbitrary work depending on worker capabilities. It does not irreversibly delete data (not Destructive), does not move money (not Financial), and does not merely read data (not Read). It is Execute — a trigger for external operations.

From the tool's definition Tool description states 'Submit independent worker tasks and wait for their results' — this allows triggering external operations (worker task execution) whose effects depend on task arguments and implementation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs run_tasks safely

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

run_tasks Rate-limited

run_tasks 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_tasks": {
      "limits": [
        {
          "counter": "run_tasks_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 Mcp Control Plane, apply this rule, and every run_tasks call is checked against it from then on.

FAQ

Questions about run_tasks

What does the run_tasks tool do? +

Submit independent worker tasks and wait for their results. It is categorised as a Execute tool in the Mcp Control Plane 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_tasks? +

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

What risk level is run_tasks? +

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

Can I rate-limit run_tasks? +

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

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

run_tasks is provided by the Mcp Control Plane MCP server (albertik322-sudo/mcp-control-plane). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Control Plane, and thousands of servers like it.

This server

All 286 Mcp Control Plane tools → High-risk tools on this server →

Across the catalogue

run on 0sec →shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

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