Update an existing list
AI agents use update_list to create or update resources in ClickUp MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ClickUp MCP Server environment.
Updates are reversible modifications that change list properties or metadata without irreversible deletion. This falls squarely in the Write category. Severity is medium because misconfigured updates to project management lists could disrupt team workflows, but the effects are not financial, not destructive (data remains recoverable), and the blast radius is limited to that specific list's team members.
From the tool's definition Tool name 'update_list' and description 'Update an existing list' indicate modification of existing data. The verb 'update' is a classic reversible write operation.
Attacks that exploit this kind of access
Update an existing list. It is categorised as a Write tool in the ClickUp MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ClickUp MCP Server MCP server in PolicyLayer and add a rule for update_list: 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 Server. Nothing to install.
update_list 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_list 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_list. 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_list is provided by the ClickUp MCP Server MCP server (yihaowang/clickup-mcp-server). 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 →