Add a watcher to a task
AI agents use add-task-watcher 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.
This tool creates or modifies task properties by adding watchers, which falls under Write category (reversible data modification). It has medium severity because adding a watcher affects task notifications and visibility for users, but the operation can be undone and does not delete data, execute arbitrary code, or cause financial impact.
From the tool's definition The tool name and description indicate it 'Add[s] a watcher to a task', which modifies task metadata by adding a user as a watcher. This is a reversible modification operation (watchers can be removed).
Attacks that exploit this kind of access
Add a watcher to a task. 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.
Register the ClickUp Operator MCP server in PolicyLayer and add a rule for add-task-watcher: 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.
add-task-watcher is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add-task-watcher 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 add-task-watcher. 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.
add-task-watcher 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 →