move_task · ClickUp MCP Server MCP: Risk & Policy

WHAT IT DOES

What move_task does on ClickUp MCP Server

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

WHY IT NEEDS A POLICY

Why move_task needs a policy

Moving a task changes its organizational context but is not irreversible (unlike deletion), does not execute arbitrary code or shell commands, and does not involve financial transactions. It is a data modification operation (Write category). Severity is medium because misuse could reorganize many tasks, causing workflow disruption, but the operation is fully reversible and non-destructive.

From the tool's definition Tool description states it 'Move[s] a task to a different list', which modifies the state and location of a task. This is a reversible operation—tasks can be moved again to their original or other locations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

move_task Rate-limited

move_task 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": {
    "move_task": {
      "limits": [
        {
          "counter": "move_task_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches ClickUp MCP Server, so you can run agents against it safely.

FAQ

Questions about move_task

What does the move_task tool do? +

Move a task to a different list. Supports direct name-based lookup for lists and tasks - no need to know IDs. It is categorised as a Write tool in the ClickUp MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on move_task? +

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

What risk level is move_task? +

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

Can I rate-limit move_task? +

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

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

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