Delete a section and move its tasks to the parent project.
AI agents call delete_section to permanently remove resources in Todoist MCP Helper — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes a section, which cannot be undone. Although tasks are moved to the parent project (mitigating data loss), the section structure itself is destroyed. Destructive operations carry inherently higher risk because they eliminate configuration or organizational state.
From the tool's definition Tool name is 'delete_section' and description explicitly states 'Delete a section' — a permanent removal operation.
Attacks that exploit this kind of access
Delete a section and move its tasks to the parent project. It is categorised as a Destructive tool in the Todoist MCP Helper MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Todoist MCP Helper MCP server in PolicyLayer and add a rule for delete_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 Helper. Nothing to install.
delete_section is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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 delete_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.
delete_section is provided by the Todoist MCP Helper MCP server (littlepeter52012/todoist-mcp-helper). 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 →