Purpose: Update an existing tag in a ClickUp space. Valid Usage: 1. Provide spaceId (preferred if available) 2. Provide spaceName (will be resolved to a space ID) Requirements: - tagName: REQUIRED - EITHER spaceId OR spaceName: REQUIRED - At least one of newTagName, tagBg, tagFg, or colorCommand ...
AI agents use update_space_tag 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.
This tool modifies existing data (tags) reversibly. It allows renaming tags and changing their color properties, which are Write operations. While the changes affect all tasks using that tag (broad impact), the modifications are reversible and do not delete or destroy data, so it is Write rather than Destructive.
From the tool's definition Tool updates an existing tag in a ClickUp space with parameters like newTagName, tagBg, tagFg. The description explicitly states 'Changes to the tag will apply to all tasks in the space that use this tag', indicating modification of data across multiple…
Attacks that exploit this kind of access
Purpose: Update an existing tag in a ClickUp space. Valid Usage: 1. Provide spaceId (preferred if available) 2. Provide spaceName (will be resolved to a space ID) Requirements: - tagName: REQUIRED - EITHER spaceId OR spaceName: REQUIRED - At least one of newTagName, tagBg, tagFg, or colorCommand must be provided Notes: - Changes to the tag will apply to all tasks in the space that use this tag - You can provide a color command (e.g.,. 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.
Register the ClickUp MCP server in PolicyLayer and add a rule for update_space_tag: 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.
update_space_tag is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_space_tag 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.
Set action: deny in the PolicyLayer policy for update_space_tag. 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.
update_space_tag 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →