Low Risk

get_user

Get a specific user by their ID

How to control get_user ↓

AI agents call get_user to retrieve information from GoHighLevel MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool retrieves user information based on an ID parameter. It performs a query/fetch operation without creating, modifying, deleting, or executing any actions. The only potential concern is information disclosure if sensitive user data is exposed, but retrieval of user profile data is a standard Read operation.

From the tool's definition Tool name 'get_user' with description 'Get a specific user by their ID' indicates a retrieval operation with no side effects.

Documented attack patterns abuse exactly the kind of access get_user gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and GoHighLevel MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_user:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_user": {}
  }
}

get_user is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register GoHighLevel MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_user tool do? +

Get a specific user by their ID. It is categorised as a Read tool in the GoHighLevel MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_user? +

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.

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 GoHighLevel MCP Server MCP server (busybee3333/go-high-level-mcp-2026-complete). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every GoHighLevel MCP Server tool call.

Deterministic rules across all 566 GoHighLevel MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

566 GoHighLevel MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.