Unified tool for creating, updating, or deleting ClickUp lists and folders. Consolidates list and folder CRUD operations. Specify type (list/folder) and action (create/update/delete). Use IDs when available (preferred) or names. Detail levels: minimal (id/name), standard (with metadata), detailed...
AI agents call manage_container 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.
Because the tool spans create/update/delete, the most severe applicable category is Destructive. Deleting a ClickUp list or folder is irreversible and can cascade to destroy all contained tasks and data, making the blast radius high if an AI agent misuses the delete action.
From the tool's definition 'deleting ClickUp lists and folders' and 'action (create/update/delete)' — the tool explicitly supports irreversible deletion of lists and folders, which can permanently remove containers and all their contents (tasks, documents, etc.).
Attacks that exploit this kind of access
Unified tool for creating, updating, or deleting ClickUp lists and folders. Consolidates list and folder CRUD operations. Specify type (list/folder) and action (create/update/delete). Use IDs when available (preferred) or names. Detail levels: minimal (id/name), standard (with metadata), detailed (all fields). 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 manage_container: 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.
manage_container 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 manage_container 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 manage_container. 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.
manage_container 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 →