Permanently delete a tag. Removes it from all tasks.
AI agents call delete_tag 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.
This tool permanently deletes data (tags) and cannot be undone. Deletion operations that affect multiple entities (all tasks using that tag) warrant Destructive classification. While the blast radius is limited to tag metadata rather than task data itself, the irreversible nature and potential to disrupt task organization across the system justifies high severity.
From the tool's definition Tool description explicitly states 'Permanently delete a tag' which is irreversible. The phrase 'Removes it from all tasks' indicates broad impact across the system.
Attacks that exploit this kind of access
Permanently delete a tag. Removes it from all tasks. 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_tag: 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_tag 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_tag 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_tag. 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_tag 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.
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 →