delete_list

PERMANENTLY deletes a ClickUp list and all its tasks. Use listId (preferred/safest) or listName. WARNING: Cannot be undone, all tasks will be deleted, listName risky if not unique.

Server ClickUp MCP twofeetup/clickup-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What delete_list does on ClickUp MCP

AI agents call delete_list 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.

Why delete_list needs a policy

This tool meets the Destructive category definition: it irreversibly deletes data (list and all associated tasks) and cannot be undone. The critical severity reflects the blast radius — an AI agent misconfigured or prompt-injected into using this tool could eliminate entire project lists and their work items. The warning about listName ambiguity adds operational risk.

From the tool's definition "PERMANENTLY deletes a ClickUp list and all its tasks" and "Cannot be undone, all tasks will be deleted" — the tool irreversibly removes data at scale without recovery option.

Questions about delete_list

What does the delete_list tool do? +

PERMANENTLY deletes a ClickUp list and all its tasks. Use listId (preferred/safest) or listName. WARNING: Cannot be undone, all tasks will be deleted, listName risky if not unique. 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.

How do I enforce a policy on delete_list? +

Register the ClickUp 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. Nothing to install.

What risk level is delete_list? +

delete_list is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_list? +

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.

How do I block delete_list completely? +

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.

What MCP server provides delete_list? +

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

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.