AI agents invoke run_due_dispatches 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.
This tool executes scheduled commands/operations in a tmux environment. While the scope is limited to already-scheduled items, the ability to forcefully trigger external dispatch operations constitutes Execute rather than Write or Read. The "legacy/emergency only" qualifier suggests this is a privileged operation with potential for unintended side effects if misused by an AI agent, warranting high severity.
From the tool's definition Tool description states "manually trigger all pending tmux dispatches that are due" - this actively executes external operations (tmux dispatches) whose effects depend on the scheduling state of the system.
Attacks that exploit this kind of access
Legacy/emergency only: manually trigger all pending tmux dispatches that are due (scheduled_at <= now). Returns the count fired. 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 run_due_dispatches: 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.
run_due_dispatches 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 run_due_dispatches 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 run_due_dispatches. 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.
run_due_dispatches 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →