New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_users_by_location

List all users assigned to a location

SERVERGoHighLevel MCP Server SOURCEbasicmachines-co/open-ghl-mcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/basicmachines-co-open-ghl-mcp/get-users-by-location.md

What get_users_by_location does on GoHighLevel MCP Server

AI agents call get_users_by_location 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_by_location is rated Low

This tool retrieves a list of users filtered by location from the GoHighLevel CRM. It performs a query operation that returns existing data without creating, modifying, deleting, or executing external actions. The blast radius of misuse is minimal—an attacker could enumerate users but cannot alter data or trigger operations. Classification: Read/low severity.

From the tool's definition Tool name contains 'get' and description states 'List all users' — both indicate data retrieval with no modification or side effects.

Risk signalsBulk/mass operation — affects multiple targets

Questions about get_users_by_location

What does the get_users_by_location tool do? +

List all users assigned to a location. 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_users_by_location? +

Register the GoHighLevel MCP Server MCP server in PolicyLayer and add a rule for get_users_by_location: 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_users_by_location? +

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

Can I rate-limit get_users_by_location? +

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

Set action: deny in the PolicyLayer policy for get_users_by_location. 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_users_by_location? +

get_users_by_location is provided by the GoHighLevel MCP Server MCP server (basicmachines-co/open-ghl-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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of GoHighLevel MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.