get_users
Get all users/team members for a location. Returns team members with their roles and permissions.
This record as markdown: /tools/busybee3333-go-high-level-mcp-2026-complete/get-users.md
What get_users does on GoHighLevel MCP Server
AI agents call get_users 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_users is rated Low
The tool retrieves and queries user/team member data without side effects. It returns information about existing users and their roles, which is a read-only data retrieval operation. While the information returned could include sensitive permissions data, the tool itself performs no actions that could cause damage or alter state, making it a Read category tool with low severity.
From the tool's definition Tool name is 'get_users' and description states it 'Get all users/team members for a location. Returns team members with their roles and permissions.' This is a retrieval operation with no modification, deletion, or execution of external operations.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs get_users 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_users, this is the rule to start with:
get_users 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_users call is checked against it from then on.
Questions about get_users
Get all users/team members for a location. Returns team members with their roles and permissions. 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_users: 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_users 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_users 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_users. 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_users 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.
More on GoHighLevel MCP Server, and thousands of servers like it.
This server
Across the catalogue