Move multiple tasks to become subtasks of another task within Todoist. This creates a hierarchical relationship where the moved tasks become children of the specified parent task. Useful for organizing related tasks or breaking down complex tasks into subtasks. Returns the updated task objects af...
AI agents use move_tasks_to_parent to create or update resources in Todoist MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Todoist MCP Server environment.
This tool creates or modifies data (task parent-child relationships) reversibly. While it reorganizes task structure, the changes are not destructive—tasks remain intact and the operation can be undone by moving tasks back or reassigning parents. The blast radius is moderate: incorrect execution could reorganize workflows and require manual cleanup, but no data is lost or financial impact occurs.
From the tool's definition The tool "move_tasks_to_parent" modifies the hierarchical structure and parent assignment of existing tasks, stated as "creates a hierarchical relationship where the moved tasks become children of the specified parent task" and "Returns the updated task…
Documented attack patterns abuse exactly the kind of access move_tasks_to_parent gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Todoist MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for move_tasks_to_parent:
{
"version": "1",
"default": "deny",
"tools": {
"move_tasks_to_parent": {
"limits": [
{
"counter": "move_tasks_to_parent_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} move_tasks_to_parent 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.
Free to start. No card required.
Move multiple tasks to become subtasks of another task within Todoist. This creates a hierarchical relationship where the moved tasks become children of the specified parent task. Useful for organizing related tasks or breaking down complex tasks into subtasks. Returns the updated task objects after successful movement with their new parent assignment. It is categorised as a Write tool in the Todoist MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Todoist MCP Server MCP server in PolicyLayer and add a rule for move_tasks_to_parent: 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 Todoist MCP Server. Nothing to install.
move_tasks_to_parent 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_tasks_to_parent 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_tasks_to_parent. 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_tasks_to_parent is provided by the Todoist MCP Server MCP server (koki-develop/todoist-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Todoist MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
32 Todoist MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.