Delete a label.
AI agents call delete_label to permanently remove resources in Todoist — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a label permanently removes a metadata organization structure from the Todoist workspace. While the blast radius is limited compared to deleting projects or tasks (which have broader dependencies), the operation is irreversible and destructive. This qualifies as Destructive rather than Write because deletion is not reversible.
From the tool's definition Tool name 'delete_label' paired with description 'Delete a label' directly indicates irreversible deletion of data. The action cannot be undone.
Attacks that exploit this kind of access
Delete a label. It is categorised as a Destructive tool in the Todoist MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Todoist MCP server in PolicyLayer and add a rule for delete_label: 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. Nothing to install.
delete_label 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_label 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_label. 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_label is provided by the Todoist MCP server (stevengonsalvez/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 →