Updates multiple tasks efficiently. For each task: use taskId (preferred) or taskName + listName. At least one update field per task. Supports assignees as array of user IDs, emails, or usernames. Configure batch size/concurrency via options. WARNING: taskName without listName will fail.
AI agents use update_bulk_tasks to create or update resources in ClickUp MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ClickUp MCP environment.
This tool modifies task data in a reversible manner (updates fields like assignees). While it operates in bulk across multiple tasks, the changes can be undone by subsequent updates. This is a Write operation, not Destructive (which would require irreversible deletion/erasure) or Execute (which would require code execution/external operations).
From the tool's definition Tool description states 'Updates multiple tasks efficiently' and 'At least one update field per task', clearly indicating modification of existing data rather than deletion or execution of arbitrary operations.
Attacks that exploit this kind of access
Updates multiple tasks efficiently. For each task: use taskId (preferred) or taskName + listName. At least one update field per task. Supports assignees as array of user IDs, emails, or usernames. Configure batch size/concurrency via options. WARNING: taskName without listName will fail. It is categorised as a Write tool in the ClickUp MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ClickUp MCP server in PolicyLayer and add a rule for update_bulk_tasks: 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. Nothing to install.
update_bulk_tasks 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 update_bulk_tasks 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 update_bulk_tasks. 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.
update_bulk_tasks is provided by the ClickUp MCP server (twofeetup/clickup-mcp). 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 →