deleteProject
AI agents call deleteProject 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.
Deleting a project is an irreversible action that destroys data and cannot be undone. This fits the Destructive category definition. The severity is high because an AI agent given this tool could accidentally delete important projects and all their contents. The confidence is 0.95 rather than higher only because the description is empty, but the name alone is sufficiently clear in intent.
From the tool's definition Tool name is 'deleteProject' with no descriptive text provided. The name strongly indicates permanent deletion of a project, which would remove the project and associated data irreversibly.
Attacks that exploit this kind of access
deleteProject. 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 deleteProject: 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.
deleteProject 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 deleteProject 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 deleteProject. 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.
deleteProject is provided by the Todoist MCP Server MCP server (stevengonsalvez/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 →