Updates an existing View. Note: ClickUp API v2 /view/{view_id} PUT endpoint currently has known issues (Internal Server Error).
AI agents use clickup_update_view 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.
The tool modifies existing data (a View object) in ClickUp without deleting or destroying it. This is a classic Write operation—changes are reversible and do not permanently eliminate data. Severity is medium because an AI agent could inadvertently change view configurations affecting team workflows, but the impact is containable through undo or reconfiguration.
From the tool's definition Tool name contains 'update' and description states it 'Updates an existing View', which is a reversible modification operation.
Documented attack patterns abuse exactly the kind of access clickup_update_view gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ClickUp MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for clickup_update_view:
{
"version": "1",
"default": "deny",
"tools": {
"clickup_update_view": {
"limits": [
{
"counter": "clickup_update_view_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} clickup_update_view 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.
Free to start. No card required.
Updates an existing View. Note: ClickUp API v2 /view/{view_id} PUT endpoint currently has known issues (Internal Server Error). 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 clickup_update_view: 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.
clickup_update_view 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 clickup_update_view 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 clickup_update_view. 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.
clickup_update_view is provided by the ClickUp MCP Server MCP server (nazruden/clickup-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ClickUp MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
31 ClickUp MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.