clickup_set_task_custom_field_value

THE RISK

Medium Risk

Why clickup_set_task_custom_field_value needs a policy

This tool modifies task metadata by updating custom field values, which is reversible. It does not delete data (not Destructive), execute arbitrary code (not Execute), involve financial transactions (not Financial), or merely retrieve information (not Read). The medium severity reflects that incorrect modifications could affect task tracking and team workflows, but changes are recoverable through updates.

From the tool's definition Tool name contains 'set_task_custom_field_value' and description states it 'Sets the value of a Custom Field on a specific task.' The verb 'sets' indicates modification of existing data.

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

POLICY

How to control clickup_set_task_custom_field_value

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_set_task_custom_field_value:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "clickup_set_task_custom_field_value": {
      "limits": [
        {
          "counter": "clickup_set_task_custom_field_value_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

Create a free account and register ClickUp MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More ClickUp MCP Server tools

Destructive clickup_delete_folder Deletes a Folder. Destructive clickup_delete_space Deletes a Space. Destructive clickup_delete_view Deletes a View. Destructive clickup_remove_task_custom_field_value Removes the value of a Custom Field from a specific task. Write clickup_create_board Create a new board view in a ClickUp space. Write clickup_create_doc Creates a new Doc within a Workspace. Write clickup_create_doc_page Creates a new page within a specific Doc. Write clickup_create_folder Creates a new Folder within a Space.

All 31 ClickUp MCP Server tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about clickup_set_task_custom_field_value

What does the clickup_set_task_custom_field_value tool do? +

Sets the value of a Custom Field on a specific task. It is categorised as a Write tool in the ClickUp MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on clickup_set_task_custom_field_value? +

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

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

Can I rate-limit clickup_set_task_custom_field_value? +

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

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

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

CHECK YOUR STACK →