Search for locations/sub-accounts in GoHighLevel with filtering options
AI agents call search_locations to retrieve information from GoHighLevel MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a search operation to retrieve and filter existing locations/sub-accounts. It has no side effects, does not create, modify, delete, or execute any actions—it only queries and returns data. This is a standard Read-category operation with minimal security risk.
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 of data.
Attacks that exploit this kind of access
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.
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.
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 GoHighLevel MCP Server MCP server (tailormadeweddings/gohighlevel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →