get-user · ClickUp Operator MCP: Risk & Policy

WHAT IT DOES

What get-user does on ClickUp Operator

AI agents call get-user to retrieve information from ClickUp Operator without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

WHY IT NEEDS A POLICY

Why get-user needs a policy

This tool retrieves user information without modifying, deleting, or executing operations. It is a straightforward read operation on user profile/account data. The blast radius is limited to information disclosure of user metadata, which is low severity.

From the tool's definition Tool name 'get-user' and description 'Get user information' indicate data retrieval with no modification or side effects.

Attacks that exploit this kind of access

Questions about get-user

What does the get-user tool do? +

Get user information. It is categorised as a Read tool in the ClickUp Operator MCP Server, which means it retrieves data without modifying state.

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

Register the ClickUp Operator MCP server in PolicyLayer and add a rule for get-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 get-user? +

get-user is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get-user? +

Yes. Add a rate_limit block to the get-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 get-user completely? +

Set action: deny in the PolicyLayer policy for get-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 get-user? +

get-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.