Move a single task (and its subtasks, if any) to a different project, section, or make it a subtask of another task. Provide the taskId and exactly one of: projectId, sectionId, or parentId.
AI agents use todoist_move_task to create or update resources in Enhanced Todoist MCP Server Extended — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Enhanced Todoist MCP Server Extended environment.
This tool modifies task metadata and structure (project/section/parent assignment) in a reversible manner. It does not create new tasks (Write creation), delete tasks (Destructive), or execute arbitrary operations (Execute). While it affects task organization, the changes can be undone by moving tasks back, making it a Write operation.
From the tool's definition "Move a single task (and its subtasks, if any) to a different project, section, or make it a subtask of another task." - modifies task hierarchy and organization by relocating tasks and their subtasks to different projects/sections/parent tasks.
Documented attack patterns abuse exactly the kind of access todoist_move_task gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Enhanced Todoist MCP Server Extended, and nothing reaches the server without passing your rules. This is the rule we recommend for todoist_move_task:
{
"version": "1",
"default": "deny",
"tools": {
"todoist_move_task": {
"limits": [
{
"counter": "todoist_move_task_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} todoist_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.
Free to start. No card required.
Move a single task (and its subtasks, if any) to a different project, section, or make it a subtask of another task. Provide the taskId and exactly one of: projectId, sectionId, or parentId. It is categorised as a Write tool in the Enhanced Todoist MCP Server Extended MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Enhanced Todoist MCP Server Extended MCP server in PolicyLayer and add a rule for todoist_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 Enhanced Todoist MCP Server Extended. Nothing to install.
todoist_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 todoist_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 todoist_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.
todoist_move_task is provided by the Enhanced Todoist MCP Server Extended MCP server (vitalio-sh/todoist-mcp-server-ext). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Enhanced Todoist MCP Server Extended, 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.
31 Enhanced Todoist MCP Server Extended tools catalogued and risk-classified — across an index of 43,000+ MCP servers.