add-task-dependency · ClickUp Operator MCP: Risk & Policy

WHAT IT DOES

What add-task-dependency does on ClickUp Operator

AI agents use add-task-dependency to create or update resources in ClickUp Operator — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ClickUp Operator environment.

WHY IT NEEDS A POLICY

Why add-task-dependency needs a policy

This tool creates or modifies task metadata (dependencies) reversibly without deleting data or executing arbitrary code. It falls under Write category as it establishes a new relationship/link between entities. Severity is medium because misuse could create circular dependencies or incorrect task hierarchies that disrupt project planning, but this is reversible through removing the dependency.

From the tool's definition Tool description states 'Add a dependency between tasks' which modifies the relationship structure between tasks in ClickUp, creating a new dependency link that did not exist before.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add-task-dependency Rate-limited

add-task-dependency stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "add-task-dependency": {
      "limits": [
        {
          "counter": "add-task-dependency_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches ClickUp Operator, so you can run agents against it safely.

FAQ

Questions about add-task-dependency

What does the add-task-dependency tool do? +

Add a dependency between tasks. It is categorised as a Write tool in the ClickUp Operator MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on add-task-dependency? +

Register the ClickUp Operator MCP server in PolicyLayer and add a rule for add-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.

What risk level is add-task-dependency? +

add-task-dependency is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit add-task-dependency? +

Yes. Add a rate_limit block to the add-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.

How do I block add-task-dependency completely? +

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

What MCP server provides add-task-dependency? +

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