Reorder sections within a project by specifying their new positions.
AI agents use todoist_sections_reorder 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.
Reordering sections is a reversible modification operation that changes data state without deleting or destroying content. It aligns with Write category (create, update, post, upload operations). Severity is medium because misuse could disrupt project organization but the action is easily undone by reordering again.
From the tool's definition Tool name contains 'reorder' and description states 'Reorder sections within a project by specifying their new positions' — this modifies the ordering state of existing sections.
Attacks that exploit this kind of access
Reorder sections within a project by specifying their new positions. 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_sections_reorder: 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_sections_reorder 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_sections_reorder 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_sections_reorder. 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_sections_reorder 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 →