delete_tag

Delete a tag. Removes it from all tasks.

Server Tick kpihx/tick-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What delete_tag does on Tick

AI agents call delete_tag to permanently remove resources in Tick — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_tag needs a policy

This tool permanently deletes a tag and removes it from all associated tasks. This is an irreversible action that cannot be undone—once deleted, the tag and its associations are lost.

From the tool's definition Tool name is 'delete_tag' and description states 'Delete a tag. Removes it from all tasks.' The verb 'Delete' combined with 'Removes it from all tasks' indicates irreversible removal of data across multiple entities.

Questions about delete_tag

What does the delete_tag tool do? +

Delete a tag. Removes it from all tasks. It is categorised as a Destructive tool in the Tick MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_tag? +

Register the Tick 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 Tick. Nothing to install.

What risk level is delete_tag? +

delete_tag is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_tag? +

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.

How do I block delete_tag completely? +

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.

What MCP server provides delete_tag? +

delete_tag is provided by the Tick MCP server (kpihx/tick-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.