Move a task to a different project in Todoist
AI agents use todoist_move_task to create or update resources in MCP Todoist — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Todoist environment.
Moving a task between projects is a reversible modification operation. The task itself is not deleted, only its project assignment changes. This constitutes a Write action rather than Destructive (which would involve deletion) or Execute (which would involve code/command execution). Severity is low because the blast radius is limited to reordering/reorganizing tasks without data loss or external system impact.
From the tool's definition Tool description states 'Move a task to a different project in Todoist' — this modifies task metadata (project association) reversibly without deleting data.
Attacks that exploit this kind of access
Move a task to a different project in Todoist. It is categorised as a Write tool in the MCP Todoist MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Todoist 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 MCP Todoist. 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 MCP Todoist MCP server (kentaroh7777/mcp-todoist). 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 →