Delete a list
AI agents call delete_list to permanently remove resources in ClickUp MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of a list in a task management system is irreversible and destroys data (the list and likely its associated tasks). This is a destructive operation with a potentially large blast radius depending on the list size and importance. While not financial, it exceeds Execute severity because the effects cannot be undone. High severity due to possible loss of multiple tasks/organization structure in one action.
From the tool's definition Tool name is 'delete_list' with description 'Delete a list'. The verb 'delete' combined with the ClickUp context indicates irreversible removal of a list and its contents.
Attacks that exploit this kind of access
Delete a list. It is categorised as a Destructive tool in the ClickUp MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ClickUp MCP Server MCP server in PolicyLayer and add a rule for delete_list: 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.
delete_list 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_list 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_list. 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_list is provided by the ClickUp MCP Server MCP server (smeric28/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 →