clickup_delete_dependency

A destructive tool on the Clickup MCP server.

SERVERClickup SOURCEtrustxai/clickup-mcp
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/clickup-mcp/clickup-delete-dependency.md

What clickup_delete_dependency does on Clickup

AI agents call clickup_delete_dependency to permanently remove resources in Clickup, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why clickup_delete_dependency is rated Critical

Delete operations are inherently destructive as they remove data that cannot be recovered through the tool itself. Removing task dependencies affects project structure irreversibly. While the blast radius is scoped to dependency relationships (not cascading deletion of tasks themselves), this remains a destructive action warranting 'high' severity.

From the tool's definition Tool name is 'clickup_delete_dependency' — the verb 'delete' indicates irreversible removal of data. No description available to provide additional context.

Questions about clickup_delete_dependency

What does the clickup_delete_dependency tool do? +

clickup_delete_dependency is a destructive tool on the Clickup MCP server. It is categorised as a Destructive tool in the Clickup 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_dependency? +

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

What risk level is clickup_delete_dependency? +

clickup_delete_dependency 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_dependency? +

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

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

clickup_delete_dependency is provided by the Clickup MCP server (trustxai/clickup-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Clickup, 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'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.