get-user
A read tool on the GoHighLevel MCP server.
This record as markdown: /tools/drausal-gohighlevel-mcp/get-user.md
What get-user does on GoHighLevel MCP Server
AI agents call get-user to retrieve information from GoHighLevel MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get-user is rated Low
This tool retrieves user information from GoHighLevel without altering any data. The 'get' prefix and action verb clearly indicate a query operation. While the user data retrieved could potentially be sensitive, the tool itself performs no destructive, financial, or executable actions.
From the tool's definition Tool name 'get-user' and description 'Get User' indicate a retrieval operation with no modification or side effects. Consistent with Read category operations (get, fetch, retrieve).
Attacks that exploit this kind of access
The rule that runs get-user safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GoHighLevel MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get-user, this is the rule to start with:
get-user is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect GoHighLevel MCP Server, apply this rule, and every get-user call is checked against it from then on.
Questions about get-user
get-user is a read tool on the GoHighLevel MCP Server MCP server. It is categorised as a Read tool in the GoHighLevel MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GoHighLevel MCP Server 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 GoHighLevel MCP Server. Nothing to install.
get-user is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
get-user is provided by the GoHighLevel MCP Server MCP server (drausal/gohighlevel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GoHighLevel MCP Server, and thousands of servers like it.
This server
Across the catalogue