run_next_agent_dispatch · Todos MCP: Risk & Policy

WHAT IT DOES

What run_next_agent_dispatch does on Todos

AI agents invoke run_next_agent_dispatch to trigger actions in Todos. 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_next_agent_dispatch needs a policy

This tool executes external agent operations, making it Execute category. Severity is high because agent dispatches can trigger arbitrary actions depending on task queue contents; misuse could cause unintended code execution or external operations. Confidence is 0.85 rather than higher because the description doesn't detail what the dispatched agents actually do or what side effects are possible.

From the tool's definition Tool description states 'Run the next queued local agent dispatch', which directly executes an external operation (agent dispatch).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_next_agent_dispatch Rate-limited

run_next_agent_dispatch 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_next_agent_dispatch": {
      "limits": [
        {
          "counter": "run_next_agent_dispatch_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 Todos, so you can run agents against it safely.

FAQ

Questions about run_next_agent_dispatch

What does the run_next_agent_dispatch tool do? +

Run the next queued local agent dispatch, optionally as a dry-run. It is categorised as a Execute tool in the Todos 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_next_agent_dispatch? +

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

What risk level is run_next_agent_dispatch? +

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

Can I rate-limit run_next_agent_dispatch? +

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

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

run_next_agent_dispatch is provided by the Todos MCP server (@hasna/todos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.