Remove a dependency from a task
AI agents call remove-task-dependency to permanently remove resources in ClickUp Operator — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a task dependency permanently deletes the dependency relationship between tasks. This action is not easily reversible as there is no indication of an undo mechanism, and restoring the dependency would require knowing the original configuration. This fits the Destructive category as it irreversibly removes data (the dependency link).
From the tool's definition 'Remove a dependency from a task' - the word 'remove' indicates an irreversible deletion of a relationship between tasks
Attacks that exploit this kind of access
Remove a dependency from a task. It is categorised as a Destructive tool in the ClickUp Operator MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ClickUp Operator MCP server in PolicyLayer and add a rule for remove-task-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 Operator. Nothing to install.
remove-task-dependency 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 remove-task-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.
Set action: deny in the PolicyLayer policy for remove-task-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.
remove-task-dependency is provided by the ClickUp Operator MCP server (noah-vh/mcp-server-clickup). 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 →