update_folder · ClickUp MCP: Risk & Policy

WHAT IT DOES

What update_folder does on ClickUp MCP

AI agents use update_folder 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 update_folder needs a policy

This tool modifies folder metadata in a reversible manner. It falls under Write rather than Execute because it updates structured data properties rather than triggering code or shell operations. Severity is medium because changes affect all lists within a folder, which could impact workflow organization, but the changes are fully reversible.

From the tool's definition Tool description states 'Updates folder properties' with fields 'name/override_statuses'. The verb 'Updates' indicates modification of existing data. Changes are reversible (folder name can be changed back, status overrides can be reverted).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_folder Rate-limited

update_folder 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": {
    "update_folder": {
      "limits": [
        {
          "counter": "update_folder_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 update_folder

What does the update_folder tool do? +

Updates folder properties. Use folderId (preferred) or folderName + (spaceId/spaceName). At least one update field (name/override_statuses) required. Changes apply to all lists in folder. 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 update_folder? +

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

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

Can I rate-limit update_folder? +

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

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

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