Low Risk

clickup_get_custom_fields

Retrieves all accessible Custom Fields for a given List.

How to control clickup_get_custom_fields ↓

What clickup_get_custom_fields does on ClickUp MCP Server

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

Low Risk

Why clickup_get_custom_fields needs a policy

This tool only retrieves metadata about custom fields in a ClickUp list. It performs no modifications, deletions, or executions. The blast radius of misuse is minimal—an agent could only enumerate field configurations, which is information disclosure at worst but does not alter state or enable further damage without companion tools.

From the tool's definition Tool name contains 'get' and description states 'Retrieves all accessible Custom Fields' — a read-only query operation with no side effects.

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

How to control clickup_get_custom_fields

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

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

clickup_get_custom_fields 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 Server — 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.

Related tools and policies

Go deeper

Questions about clickup_get_custom_fields

What does the clickup_get_custom_fields tool do? +

Retrieves all accessible Custom Fields for a given List. It is categorised as a Read tool in the ClickUp MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on clickup_get_custom_fields? +

Register the ClickUp MCP Server MCP server in PolicyLayer and add a rule for clickup_get_custom_fields: 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 clickup_get_custom_fields? +

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

Can I rate-limit clickup_get_custom_fields? +

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

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

clickup_get_custom_fields is provided by the ClickUp MCP Server MCP server (nazruden/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 Server tool call.

Start from ClickUp MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

31 ClickUp MCP Server 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.