This record as markdown: /tools/todos/delete-label.md
What delete_label does on Todos
AI agents call delete_label to permanently remove resources in Todos, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_label is rated Critical
This tool irreversibly removes a label from the task management system. While the blast radius is somewhat contained (labels are typically metadata rather than core task data), the permanent deletion of labels could disrupt task organization, filtering, and any dependent workflows if labels are referenced elsewhere. This fits the Destructive category as it cannot be undone and destroys data.
From the tool's definition Tool name is 'delete_label' and description states 'Permanently delete a label.' The use of 'Permanently delete' explicitly indicates an irreversible action that destroys data.
Attacks that exploit this kind of access
The rule that runs delete_label safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Todos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_label, this is the rule to start with:
delete_label is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Todos, apply this rule, and every delete_label call is checked against it from then on.
Questions about delete_label
Permanently delete a label. It is categorised as a Destructive tool in the Todos MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Todos 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 Todos. 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 Todos MCP server (@hasna/todos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Todos, and thousands of servers like it.
Across the catalogue