task_comments · ClickUp MCP: Risk & Policy

WHAT IT DOES

What task_comments does on ClickUp MCP

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

WHY IT NEEDS A POLICY

Why task_comments needs a policy

The primary concern is the 'create' action that adds new comments to tasks. While the tool also includes a 'get' action (Read), the most severe capability is comment creation, which is a reversible write operation. The ability to mention users and trigger notifications elevates this above a simple Read operation. However, comments can typically be edited or deleted, making it Write rather than Destructive.

From the tool's definition Tool description explicitly states 'create (add new comment)' as an action, which modifies task state by adding new comments. Comments can 'mention users and notify assignees', indicating side effects that alter notification state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

task_comments Rate-limited

task_comments 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": {
    "task_comments": {
      "limits": [
        {
          "counter": "task_comments_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, so you can run agents against it safely.

FAQ

Questions about task_comments

What does the task_comments tool do? +

Manage task comments. Actions: get (retrieve comments), create (add new comment). Flexible task identification: taskId, taskName, or customTaskId. Comments can mention users and notify assignees. It is categorised as a Write tool in the ClickUp MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on task_comments? +

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

What risk level is task_comments? +

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

Can I rate-limit task_comments? +

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

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

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