Move a task to a different section in Todoist
AI agents use move-task-to-section to create or update resources in Todoist MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Todoist MCP environment.
This tool changes the state of an existing task by reassigning its section, which is a reversible modification. It does not delete data (would be Destructive), execute code (would be Execute), or create financial transactions (would be Financial). It modifies task organization within Todoist, fitting the Write category.
From the tool's definition Tool name 'move-task-to-section' and description 'Move a task to a different section in Todoist' indicate the tool modifies task metadata (section assignment) without deleting data or executing external operations.
Attacks that exploit this kind of access
Move a task to a different section in Todoist. It is categorised as a Write tool in the Todoist MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Todoist MCP server in PolicyLayer and add a rule for move-task-to-section: 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. Nothing to install.
move-task-to-section 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-to-section 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-to-section. 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-to-section is provided by the Todoist MCP server (scofieldkoh/todoist_mcp). 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 →