Delete a tag from the system. Removes the tag and all its associations with tasks. Args: tag_name: Name of the tag to delete Returns: Confirmation with tag name and affected task count
AI agents call delete_tag to permanently remove resources in Taskdog — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes data (a tag and its associations) and cannot be undone. While the impact is scoped to tag metadata rather than core task data, the irreversible nature and potential to cascade deletions across multiple task-tag relationships makes this Destructive rather than Write. An agent could mistakenly delete important organizational tags, disrupting task categorization.
From the tool's definition The tool description explicitly states it 'Delete a tag from the system' and 'Removes the tag and all its associations with tasks.' The use of 'Delete' and 'Removes' indicates irreversible data deletion.
Documented attack patterns abuse exactly the kind of access delete_tag gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Taskdog, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_tag:
{
"version": "1",
"default": "deny",
"hide": [
"delete_tag"
]
}delete_tag disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a tag from the system. Removes the tag and all its associations with tasks. Args: tag_name: Name of the tag to delete Returns: Confirmation with tag name and affected task count. It is categorised as a Destructive tool in the Taskdog MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Taskdog 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 Taskdog. 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 Taskdog MCP server (kohei-wada/taskdog). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Taskdog, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
26 Taskdog tools catalogued and risk-classified — across an index of 43,000+ MCP servers.