clickup_merge_tasks

A write tool on the Clickup MCP server.

SERVERClickup SOURCEtrustxai/clickup-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What clickup_merge_tasks does on Clickup

AI agents use clickup_merge_tasks to create or update resources in Clickup, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Clickup environment.

RISK

Why clickup_merge_tasks is rated Medium

Merging tasks modifies data structures by combining two tasks into one, which is a reversible write operation. While it affects data state, it is not destructive (the underlying information persists, though reorganized) and not financial.

From the tool's definition Tool name 'clickup_merge_tasks' indicates modification of task data through a merge operation. Description is empty, limiting specificity.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs clickup_merge_tasks safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Clickup, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For clickup_merge_tasks, this is the rule to start with:

clickup_merge_tasks Rate-limited

clickup_merge_tasks stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "clickup_merge_tasks": {
      "limits": [
        {
          "counter": "clickup_merge_tasks_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Clickup, apply this rule, and every clickup_merge_tasks call is checked against it from then on.

FAQ

Questions about clickup_merge_tasks

What does the clickup_merge_tasks tool do? +

clickup_merge_tasks is a write tool on the Clickup MCP server. It is categorised as a Write tool in the Clickup MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on clickup_merge_tasks? +

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

What risk level is clickup_merge_tasks? +

clickup_merge_tasks is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

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 (trustxai/clickup-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Clickup, and thousands of servers like it.

This server

All 166 Clickup tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →