dispatch_to_multiple · Todos MCP: Risk & Policy

WHAT IT DOES

What dispatch_to_multiple does on Todos

AI agents invoke dispatch_to_multiple 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 dispatch_to_multiple needs a policy

This tool dispatches tasks to multiple tmux windows, which constitutes triggering external operations (executing commands/tasks across multiple terminal sessions). The fan-out nature means a single misuse could propagate commands to many windows simultaneously, increasing the blast radius significantly.

From the tool's definition 'fan-out: send the same tasks or task list to multiple tmux windows in sequence' and 'A stagger delay is applied between each window'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

dispatch_to_multiple Rate-limited

dispatch_to_multiple 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": {
    "dispatch_to_multiple": {
      "limits": [
        {
          "counter": "dispatch_to_multiple_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 dispatch_to_multiple

What does the dispatch_to_multiple tool do? +

Legacy/emergency fan-out: send the same tasks or task list to multiple tmux windows in sequence after a human explicitly chooses tmux delivery. A stagger delay is applied between each window. 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 dispatch_to_multiple? +

Register the Todos MCP server in PolicyLayer and add a rule for dispatch_to_multiple: 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 dispatch_to_multiple? +

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

Can I rate-limit dispatch_to_multiple? +

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

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

dispatch_to_multiple 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.