Purpose: Delete a tag from 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 Warning: - This will remove the tag from all tasks in the space - Th...
AI agents call delete_space_tag to permanently remove resources in ClickUp MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes a tag across all tasks in a space, removing metadata from potentially many items. The description explicitly states the action cannot be undone, making it destructive rather than merely a write operation. The blast radius affects all tasks using that tag throughout the space, warranting high severity.
From the tool's definition 'Delete a tag from a ClickUp space', 'This will remove the tag from all tasks in the space', 'This action cannot be undone'
Attacks that exploit this kind of access
Purpose: Delete a tag from 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 Warning: - This will remove the tag from all tasks in the space - This action cannot be undone. It is categorised as a Destructive tool in the ClickUp MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ClickUp MCP server in PolicyLayer and add a rule for delete_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.
delete_space_tag is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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 delete_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.
delete_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 →