delete_bulk_tasks

PERMANENTLY deletes multiple tasks. For each task: use taskId (preferred/safest) or taskName + listName. Configure batch size/concurrency via options. WARNING: Cannot be undone, taskName without listName is dangerous.

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

What delete_bulk_tasks does on ClickUp MCP

AI agents call delete_bulk_tasks 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_bulk_tasks needs a policy

This tool irreversibly deletes data at scale (bulk operations). The description explicitly warns that the action 'Cannot be undone' and that using taskName without listName is 'dangerous', indicating potential for unintended mass deletion. Destructive actions represent the highest risk when misused by an AI agent, as they destroy information that cannot be recovered.

From the tool's definition PERMANENTLY deletes multiple tasks... Cannot be undone

Questions about delete_bulk_tasks

What does the delete_bulk_tasks tool do? +

PERMANENTLY deletes multiple tasks. For each task: use taskId (preferred/safest) or taskName + listName. Configure batch size/concurrency via options. WARNING: Cannot be undone, taskName without listName is dangerous. 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_bulk_tasks? +

Register the ClickUp MCP server in PolicyLayer and add a rule for delete_bulk_tasks: 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_bulk_tasks? +

delete_bulk_tasks 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_bulk_tasks? +

Yes. Add a rate_limit block to the delete_bulk_tasks 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_bulk_tasks completely? +

Set action: deny in the PolicyLayer policy for delete_bulk_tasks. 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_bulk_tasks? +

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