dispatch_to_multiple
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.
This record as markdown: /tools/todos/dispatch-to-multiple.md
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 dispatch_to_multiple is rated High
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
The rule that runs dispatch_to_multiple safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Todos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For dispatch_to_multiple, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Todos, apply this rule, and every dispatch_to_multiple call is checked against it from then on.
Questions about dispatch_to_multiple
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.
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.
dispatch_to_multiple is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
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.
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.
More on Todos, and thousands of servers like it.
Across the catalogue