delete_section

THE RISK

Critical Risk

Why delete_section needs a policy

This tool irreversibly deletes data (a section) and cannot be undone. Although tasks are preserved by moving to the project, the section itself is permanently removed. This meets the definition of Destructive category, which applies to actions that 'irreversibly deletes or overwrites data, or actions that cannot be undone (delete, drop, purge, force-push)'.

From the tool's definition Tool description explicitly states 'Permanently delete a Todoist section' and 'This action will remove the section'. The word 'Permanently' and 'delete' clearly indicate irreversible data removal.

Documented attack patterns abuse exactly the kind of access delete_section gives an agent:

POLICY

How to control delete_section

PolicyLayer is an MCP gateway — it sits between your AI agents and Todoist MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_section:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_section"
  ]
}

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.

Create a free account and register Todoist MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Todoist MCP Server tools

Destructive delete_comment Permanently delete a comment by its unique identifier. This action will remove the comment Destructive delete_label PERMANENTLY delete a personal label by its ID. WARNING: This action is IRREVERSIBLE and wi Destructive delete_project Permanently delete a Todoist project by its unique identifier. This action will remove the Destructive delete_task Permanently delete a Todoist task by its unique identifier. This action will remove the ta Write close_task Mark a Todoist task as completed. This action moves the task to the completed state while Write create_label Create a new personal label with customizable properties including name, color, display or Write create_project Create a new Todoist project with customizable settings. Allows you to set up a project wi Write create_project_comment Add a comment to a specific Todoist project. Supports rich text content and optional file

All 32 Todoist MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Todoist MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about delete_section

What does the delete_section tool do? +

Permanently delete a Todoist section by its unique identifier. This action will remove the section and move any tasks in this section to the project. 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.

How do I enforce a policy on delete_section? +

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.

What risk level is delete_section? +

delete_section is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_section? +

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.

How do I block delete_section completely? +

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.

What MCP server provides delete_section? +

delete_section is provided by the Todoist MCP Server MCP server (koki-develop/todoist-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Todoist MCP Server tool call.

Start from Todoist MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →