search_locations
Search for locations/sub-accounts in GoHighLevel with filtering options
This record as markdown: /tools/ghl/search-locations.md
What search_locations does on Ghl
AI agents call search_locations to retrieve information from Ghl without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
skip | number | — | Number of results to skip for pagination (default: 0) |
email | string | — | Filter by email address |
limit | number | — | Maximum number of locations to return (default: 10) |
order | string | — | Order of results (default: asc) |
companyId | string | — | Company/Agency ID to filter locations |
Parameters from the server's own tool schema.
Why search_locations is rated Low
This tool retrieves or searches for existing location and sub-account data without creating, modifying, deleting, or executing any operations. It is a standard read-only query function with no side effects on the system.
From the tool's definition Tool name 'search_locations' and description 'Search for locations/sub-accounts in GoHighLevel with filtering options' indicate a query/retrieval operation with no modification or execution.
Attacks that exploit this kind of access
The rule that runs search_locations safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ghl, 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 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 Ghl, apply this rule, and every search_locations call is checked against it from then on.
Questions about search_locations
Search for locations/sub-accounts in GoHighLevel with filtering options. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
search_locations accepts 5 parameters: skip, email, limit, order, companyId. The full parameter table on this page comes from the server's own tool schema.
Register the Ghl 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 Ghl. Nothing to install.
search_locations 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 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.
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.
search_locations is provided by the Ghl MCP server (ghl-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ghl, and thousands of servers like it.
This server
Across the catalogue