Move a section to a different project. All tasks in the section will move with it.
AI agents use todoist_section_move 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.
This tool modifies existing data (section location and task associations) in a reversible manner—the section and its tasks can be moved back to the original project. It does not delete data (which would be Destructive) nor execute arbitrary code (which would be Execute).
From the tool's definition Tool description states 'Move a section to a different project. All tasks in the section will move with it.' The 'move' operation modifies the organizational structure and task associations within Todoist, affecting data locations and project assignments.
Attacks that exploit this kind of access
Move a section to a different project. All tasks in the section will move with it. 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_section_move: 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_section_move 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_section_move 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_section_move. 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_section_move is provided by the Mcp Todoist MCP server (@greirson/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 →