clickup_merge_tasks

Merge multiple tasks into a single task. The primary task will retain all data, and secondary tasks will be deleted after merging their content.

SERVERClickUp MCP Server - Enhanced SOURCEchykalophia/clickup-mcp-server---enhanced
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/chykalophia-clickup-mcp-server-enhanced/clickup-merge-tasks.md

What clickup_merge_tasks does on ClickUp MCP Server - Enhanced

AI agents call clickup_merge_tasks to permanently remove resources in ClickUp MCP Server - Enhanced, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why clickup_merge_tasks is rated Critical

The tool irreversibly deletes secondary tasks after merging them into the primary task. Deletion of tasks cannot be undone, making this a Destructive operation. The blast radius is high because an AI agent misusing this tool could permanently destroy multiple tasks and their associated data across a workspace.

From the tool's definition secondary tasks will be deleted after merging their content

Questions about clickup_merge_tasks

What does the clickup_merge_tasks tool do? +

Merge multiple tasks into a single task. The primary task will retain all data, and secondary tasks will be deleted after merging their content. It is categorised as a Destructive tool in the ClickUp MCP Server - Enhanced 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 clickup_merge_tasks? +

Register the ClickUp MCP Server - Enhanced MCP server in PolicyLayer and add a rule for clickup_merge_tasks: 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 ClickUp MCP Server - Enhanced. Nothing to install.

What risk level is clickup_merge_tasks? +

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

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

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

clickup_merge_tasks is provided by the ClickUp MCP Server - Enhanced MCP server (chykalophia/clickup-mcp-server---enhanced). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on ClickUp MCP Server - Enhanced, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of ClickUp MCP Server - Enhanced's. Pull the full record:

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.