edit-user · ClickUp Operator MCP: Risk & Policy

WHAT IT DOES

What edit-user does on ClickUp Operator

AI agents use edit-user 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.

WHY IT NEEDS A POLICY

Why edit-user needs a policy

Editing a user modifies workspace user data (name, email, role, permissions, etc.) reversibly. This is less severe than deletion (Destructive) but more impactful than simple data creation (Write). The medium severity reflects that unauthorized user edits could disrupt workspace access, permissions, or user management, but the changes can be undone.

From the tool's definition Tool name 'edit-user' and description 'Edit a user in a workspace' indicate modification of user data. This is a reversible write operation that changes existing user records.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

edit-user Rate-limited

edit-user 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "edit-user": {
      "limits": [
        {
          "counter": "edit-user_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches ClickUp Operator, so you can run agents against it safely.

FAQ

Questions about edit-user

What does the edit-user tool do? +

Edit a user in a workspace. 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.

How do I enforce a policy on edit-user? +

Register the ClickUp Operator MCP server in PolicyLayer and add a rule for edit-user: 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.

What risk level is edit-user? +

edit-user is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit edit-user? +

Yes. Add a rate_limit block to the edit-user 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.

How do I block edit-user completely? +

Set action: deny in the PolicyLayer policy for edit-user. 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.

What MCP server provides edit-user? +

edit-user 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.