Permanently delete a project and all its tasks
AI agents call delete_project 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 permanently deletes a project and cascades deletion to all contained tasks. This is irreversible data destruction with no undo mechanism. While not financial in nature, the permanent loss of user data (potentially many tasks and associated metadata) represents high severity. An AI agent misusing this without explicit user confirmation could cause significant productivity loss and frustration.
From the tool's definition Tool explicitly stated as 'Permanently delete a project and all its tasks' - uses word 'Permanently' and 'delete', indicating irreversible removal of data.
Attacks that exploit this kind of access
Permanently delete a project 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_project: 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_project 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_project 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_project. 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_project is provided by the Todoist MCP Server MCP server (rauf543/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 →