ClickUp Operator

65 tools. 44 can modify or destroy data without limits.

11 destructive tools with no built-in limits. Policy required.

Last updated:

44 can modify or destroy data
21 read-only
65 tools total

Community server · catalogue entry verified 28/06/2026

How to control ClickUp Operator ↓

What ClickUp Operator exposes to your agents

Read (21) Write / Execute (33) Destructive / Financial (11)
Critical Risk

The most dangerous ClickUp Operator tools

44 of ClickUp Operator's 65 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

How to control ClickUp Operator

PolicyLayer is an MCP gateway — it sits between your AI agents and ClickUp Operator, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations
{
  "delete-checklist": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations
{
  "add-guest-to-folder": {
    "limits": [
      {
        "counter": "add-guest-to-folder_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "get-authorized-user": {
    "limits": [
      {
        "counter": "get-authorized-user_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

  1. Create a free account and register ClickUp Operator — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON CLICKUP OPERATOR →

Instant setup, no code required.

All 65 ClickUp Operator tools

WRITE 32 tools
Write add-guest-to-folder Add a guest to a folder Write add-guest-to-list Add a guest to a list Write add-guest-to-task Add a guest to a task Write add-tags-to-time-entries Add tags to time entries Write add-task-dependency Add a dependency between tasks Write add-task-watcher Add a watcher to a task Write create-checklist Create a checklist in a task Write create-checklist-item Create an item in a checklist Write create-folder Create a new folder in a space Write create-folderless-list Create a list directly in a space without a folder Write create-goal Create a new goal in a team Write create-space Create a new space in a team Write create-space-tag Create a new tag in a space Write create-task Create a new task in a list Write create-task-comment Create a comment on a task Write create-task-from-template Create a task from a template Write create-team-group Create a team (user group) Write create-team-view Create a team view Write create-webhook Create a webhook Write edit-checklist Edit a checklist Write edit-guest Edit a guest Write edit-user Edit a user in a workspace Write invite-guest Invite a guest to a workspace Write invite-user Invite a user to a workspace Write remove-tags-from-time-entries Remove tags from time entries Write stop-time-entry Stop time tracking for a task Write update-comment Update a comment Write update-task Update a task Write update-team-group Update a team (user group) Write update-time-entry Update a time entry Write update-time-entry-tag Update a time entry tag Write update-webhook Update a webhook

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

Questions about ClickUp Operator

Can an AI agent delete data through the ClickUp Operator MCP server? +

Yes. The ClickUp Operator server exposes 11 destructive tools including delete-checklist, delete-comment, delete-team-group. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through ClickUp Operator? +

The ClickUp Operator server has 32 write tools including add-guest-to-folder, add-guest-to-list, add-guest-to-task. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach ClickUp Operator.

How many tools does the ClickUp Operator MCP server expose? +

65 tools across 4 categories: Destructive, Execute, Read, Write. 21 are read-only. 44 can modify, create, or delete data.

How do I enforce a policy on ClickUp Operator? +

Register the ClickUp Operator MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every ClickUp Operator tool call.

Deterministic rules across all 65 ClickUp Operator tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Instant setup, no code required.

65 ClickUp Operator tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.