clickup_delete_subtask

⚠️ DESTRUCTIVE: Delete a subtask from ClickUp. This action cannot be undone and will permanently remove the subtask.

SERVERClickUp MCP Server - Enhanced SOURCEchykalophia/clickup-mcp-server---enhanced
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/chykalophia-clickup-mcp-server-enhanced/clickup-delete-subtask.md

What clickup_delete_subtask does on ClickUp MCP Server - Enhanced

AI agents call clickup_delete_subtask to permanently remove resources in ClickUp MCP Server - Enhanced, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why clickup_delete_subtask is rated Critical

This tool permanently deletes a subtask with no undo capability, fitting the Destructive category definition. While the impact is scoped to a single subtask (limiting blast radius compared to bulk operations), the irreversible nature and explicit warning elevate severity to high rather than medium. Confidence is very high due to explicit destructive language in the description.

From the tool's definition Tool description explicitly states '⚠️ DESTRUCTIVE: Delete a subtask from ClickUp. This action cannot be undone and will permanently remove the subtask.' The use of 'delete', 'cannot be undone', and 'permanently remove' clearly indicates irreversible data…

Questions about clickup_delete_subtask

What does the clickup_delete_subtask tool do? +

⚠️ DESTRUCTIVE: Delete a subtask from ClickUp. This action cannot be undone and will permanently remove the subtask. It is categorised as a Destructive tool in the ClickUp MCP Server - Enhanced 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 clickup_delete_subtask? +

Register the ClickUp MCP Server - Enhanced MCP server in PolicyLayer and add a rule for clickup_delete_subtask: 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 - Enhanced. Nothing to install.

What risk level is clickup_delete_subtask? +

clickup_delete_subtask 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 clickup_delete_subtask? +

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

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

clickup_delete_subtask is provided by the ClickUp MCP Server - Enhanced MCP server (chykalophia/clickup-mcp-server---enhanced). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on ClickUp MCP Server - Enhanced, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of ClickUp MCP Server - Enhanced's. Pull the full record:

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.