move_task
Re-parent a task to another project and/or task list, preserving its id and history.
This record as markdown: /tools/todos/move-task.md
What move_task does on Todos
AI agents use move_task to create or update resources in Todos, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Todos environment.
Why move_task is rated Medium
The tool modifies task relationships and organizational structure but does not delete, destroy, or create financial obligations. It is reversible (tasks can be moved again), so it is Write rather than Destructive. The severity is medium because misuse could reorganize tasks in confusing ways, but the operation is non-destructive and the blast radius is limited to task organization within the system.
From the tool's definition Tool description states it "Re-parent a task to another project and/or task list, preserving its id and history." This is a modification operation that changes task metadata (parent/project association) but is reversible—tasks can be moved back or reorganized.
Attacks that exploit this kind of access
The rule that runs move_task 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 move_task, this is the rule to start with:
move_task stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 move_task call is checked against it from then on.
Questions about move_task
Re-parent a task to another project and/or task list, preserving its id and history. It is categorised as a Write tool in the Todos MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Todos MCP server in PolicyLayer and add a rule for move_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 Todos. Nothing to install.
move_task is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the move_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 move_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.
move_task 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.
This server
Across the catalogue