Low Risk

get_threaded_comments

Get threaded comments (replies) for a parent comment. Returns comment details with pagination support.

How to control get_threaded_comments ↓

AI agents call get_threaded_comments to retrieve information from ClickUp MCP Sedrver without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool retrieves and displays existing comment data from ClickUp. It performs a query operation that returns information without creating, modifying, deleting, or executing any actions. The pagination support is a typical read operation feature. No data is changed, and there are no irreversible effects or external operations triggered.

From the tool's definition Tool name contains 'get' and description states 'Get threaded comments (replies) for a parent comment. Returns comment details with pagination support.' The verb 'Get' and 'Returns' indicate a read-only retrieval operation with no modification or side effects.

Documented attack patterns abuse exactly the kind of access get_threaded_comments 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 get_threaded_comments:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_threaded_comments": {}
  }
}

get_threaded_comments is read-only, so it stays allowed — but 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.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_threaded_comments tool do? +

Get threaded comments (replies) for a parent comment. Returns comment details with pagination support. It is categorised as a Read tool in the ClickUp MCP Sedrver MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_threaded_comments? +

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

What risk level is get_threaded_comments? +

get_threaded_comments is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_threaded_comments? +

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

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

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