Delete a section and all its tasks
AI agents call delete_section to permanently remove resources in Todoist MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes data (a section and all its associated tasks) with no undo mechanism. This is a classic Destructive operation. The cascade effect of deleting all child tasks makes this particularly severe. While not Financial, it has high blast radius if invoked unintentionally by an AI agent, as the deletion cannot be reversed.
From the tool's definition Tool name is 'delete_section' and description states 'Delete a section and all its tasks' - both clearly indicate irreversible deletion of data. The operation cascades to delete all tasks within the section, compounding the destructive impact.
Attacks that exploit this kind of access
Delete a section and all its tasks. It is categorised as a Destructive tool in the Todoist MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Todoist MCP Server 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 Server. 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 Server MCP server (rfbatista/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 →