search_locations

Search for locations/sub-accounts in GoHighLevel with filtering options

SERVERGoHighLevel MCP Server SOURCEhridayshah7/gohighlevel-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/hridayshah7-gohighlevel-mcp/search-locations.md

WHAT IT DOES

What search_locations does on GoHighLevel MCP Server

AI agents call search_locations 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.

RISK

Why search_locations is rated Low

The tool performs a search operation that retrieves location and sub-account data from GoHighLevel. 'Search' is fundamentally a read-only operation that queries existing data without creating, modifying, or deleting anything.

From the tool's definition Tool name 'search_locations' and description 'Search for locations/sub-accounts in GoHighLevel with filtering options' indicates a query/retrieval operation with no modification or deletion capability.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs search_locations 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 search_locations, this is the rule to start with:

search_locations Allowed

search_locations is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect GoHighLevel MCP Server, apply this rule, and every search_locations call is checked against it from then on.

FAQ

Questions about search_locations

What does the search_locations tool do? +

Search for locations/sub-accounts in GoHighLevel with filtering options. 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 search_locations? +

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

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

Can I rate-limit search_locations? +

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

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

search_locations is provided by the GoHighLevel MCP Server MCP server (hridayshah7/gohighlevel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on GoHighLevel MCP Server, and thousands of servers like it.

This server

All 255 GoHighLevel MCP Server tools →

Across the catalogue

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →hybrid_search on Azure AI Agent Service + Azure AI Search MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →