Delete a section by its ID
AI agents call todoist_delete_section to permanently remove resources in Enhanced Todoist MCP Server Extended — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a section irreversibly removes an organizational container and typically cascades deletion or reorganization of contained tasks. This cannot be undone and represents permanent data loss, making it Destructive rather than Write. High severity reflects potential loss of structured task organization and associated work.
From the tool's definition Tool name explicitly includes 'delete' and description states 'Delete a section by its ID'. Sections contain tasks and are structural containers within Todoist projects.
Documented attack patterns abuse exactly the kind of access todoist_delete_section gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Enhanced Todoist MCP Server Extended, and nothing reaches the server without passing your rules. This is the rule we recommend for todoist_delete_section:
{
"version": "1",
"default": "deny",
"hide": [
"todoist_delete_section"
]
} todoist_delete_section disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a section by its ID. It is categorised as a Destructive tool in the Enhanced Todoist MCP Server Extended MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Enhanced Todoist MCP Server Extended MCP server in PolicyLayer and add a rule for todoist_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 Enhanced Todoist MCP Server Extended. Nothing to install.
todoist_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 todoist_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 todoist_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.
todoist_delete_section is provided by the Enhanced Todoist MCP Server Extended MCP server (vitalio-sh/todoist-mcp-server-ext). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Enhanced Todoist MCP Server Extended, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
31 Enhanced Todoist MCP Server Extended tools catalogued and risk-classified — across an index of 43,000+ MCP servers.