Update a user group
AI agents use update_user_group 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 creates or modifies data (a user group) in a reversible manner—updates can be undone, reverted, or modified further. This is characteristic of Write category. It does not delete irreversibly (Destructive), execute arbitrary code (Execute), involve financial transactions (Financial), or retrieve data only (Read).
From the tool's definition Tool name 'update_user_group' and description 'Update a user group' indicates modification of existing data (a user group's properties or membership). The ClickUp MCP Server context confirms this operates on workspace hierarchy management.
Attacks that exploit this kind of access
Update a user group. 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_user_group: 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_user_group 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_user_group 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_user_group. 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_user_group is provided by the ClickUp MCP Server MCP server (smeric28/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 →