handoff_task
Hand off a task from its current Agent to another Agent. Cancels the active assignment (if any) and creates a fresh assignment + run for the target Agent, recording a handoff event on the timeline. Use this to transfer live work when an Agent is blocked, finished its part, or a more suitable Agen...
This record as markdown: /tools/todo-for-ai-todo-for-ai-mcp/handoff-task.md
What handoff_task does on Todo for AI MCP Server
AI agents invoke handoff_task to trigger actions in Todo for AI MCP Server. 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 handoff_task is rated High
handoff_task triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
The rule that runs handoff_task safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Todo for AI MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For handoff_task, this is the rule to start with:
handoff_task 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 Todo for AI MCP Server, apply this rule, and every handoff_task call is checked against it from then on.
Questions about handoff_task
Hand off a task from its current Agent to another Agent. Cancels the active assignment (if any) and creates a fresh assignment + run for the target Agent, recording a handoff event on the timeline. Use this to transfer live work when an Agent is blocked, finished its part, or a more suitable Agent should take over. It is categorised as a Execute tool in the Todo for AI MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Todo for AI MCP Server MCP server in PolicyLayer and add a rule for handoff_task: 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 Todo for AI MCP Server. Nothing to install.
handoff_task 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 handoff_task 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 handoff_task. 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.
handoff_task is provided by the Todo for AI MCP Server MCP server (todo-for-ai/todo-for-ai-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Todo for AI MCP Server, and thousands of servers like it.
Across the catalogue