Medium Risk

create_task_comment

Create a new comment on a ClickUp task. Supports optional assignee and notification settings.

How to control create_task_comment ↓

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

Medium Risk

This tool modifies data by adding a new comment to an existing task. Comments are reversible (can be edited or deleted), making this a Write operation rather than Execute or Destructive. The severity is medium because while comments can affect team communication and trigger notifications, they don't cause irreversible data loss or financial impact.

From the tool's definition Tool creates a new comment on a ClickUp task, which is a reversible write operation. The description explicitly states 'Create a new comment' and includes optional parameters for assignee and notification settings.

Documented attack patterns abuse exactly the kind of access create_task_comment gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and ClickUp MCP Sedrver, and nothing reaches the server without passing your rules. This is the rule we recommend for create_task_comment:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_task_comment": {
      "limits": [
        {
          "counter": "create_task_comment_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

create_task_comment 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.

  1. Create a free account and register ClickUp MCP Sedrver — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the create_task_comment tool do? +

Create a new comment on a ClickUp task. Supports optional assignee and notification settings. It is categorised as a Write tool in the ClickUp MCP Sedrver MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_task_comment? +

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

What risk level is create_task_comment? +

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

Can I rate-limit create_task_comment? +

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

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

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

Enforce policy on every ClickUp MCP Sedrver tool call.

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

Free to start. No card required.

42 ClickUp MCP Sedrver tools catalogued and risk-classified — across an index of 42,500+ 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.