merge_tags

Merge one tag into another. Tasks with source get target instead; source is deleted.

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

What merge_tags does on Tick

AI agents call merge_tags 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 merge_tags needs a policy

The tool permanently deletes the source tag and reassigns all associated tasks, making it irreversible. The deletion of the source tag and mass reassignment of tasks across potentially many items constitutes a destructive operation with a high blast radius if misused.

From the tool's definition 'source is deleted' — the source tag is irreversibly deleted after merging; tasks with source get target instead

Questions about merge_tags

What does the merge_tags tool do? +

Merge one tag into another. Tasks with source get target instead; source is deleted. 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 merge_tags? +

Register the Tick MCP server in PolicyLayer and add a rule for merge_tags: 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 merge_tags? +

merge_tags 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 merge_tags? +

Yes. Add a rate_limit block to the merge_tags 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 merge_tags completely? +

Set action: deny in the PolicyLayer policy for merge_tags. 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 merge_tags? +

merge_tags 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.