Delete a task found by ID or partial name search (case-insensitive)
AI agents call todoist_task_delete to permanently remove resources in Mcp Todoist — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes data (tasks) from Todoist without the ability to undo the action through normal means. Task deletion is irreversible and represents data loss. While the blast radius is bounded to a single user's Todoist workspace (not system-wide or financial), the destructive nature of permanently removing user data warrants 'high' severity.
From the tool's definition Tool name contains 'delete' and description explicitly states 'Delete a task'. The function performs irreversible deletion of task data from a user's task management system.
Attacks that exploit this kind of access
Delete a task found by ID or partial name search (case-insensitive). It is categorised as a Destructive tool in the Mcp Todoist MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Todoist MCP server in PolicyLayer and add a rule for todoist_task_delete: 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_task_delete 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_task_delete 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_task_delete. 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_task_delete 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 →