get_users_by_location

THE RISK

Low Risk

Why get_users_by_location needs a policy

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

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

POLICY

How to control get_users_by_location

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_users_by_location:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_users_by_location": {}
  }
}

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

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

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More GoHighLevel MCP Server tools

Destructive delete_appointment Delete an appointment Destructive delete_contact Delete a contact from GoHighLevel Destructive delete_contact_note Delete a note from a contact Destructive delete_contact_task Delete a task from a contact Destructive delete_custom_field Delete a custom field Destructive delete_custom_value Delete a custom value Destructive delete_opportunity Delete an opportunity from GoHighLevel Destructive delete_user Delete a user

All 64 GoHighLevel MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

Roll out MCP under one policy → Per-person scoped tokens, one central policy, and full audit across every server your team connects.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →
PolicyLayer vs alternatives → How deterministic, per-call MCP policy compares with gateways, identity layers, and authorisation platforms.

FAQ

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.

Enforce policy on every GoHighLevel MCP Server tool call.

Start from GoHighLevel MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →