Get locations by stripeCustomerId or stripeSubscriptionId with companyId
AI agents call locations-deprecated 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 retrieves location information without modifying, deleting, or executing operations. However, severity is medium rather than low because: (1) locations data in business management systems often contains sensitive operational information (addresses, coordinates), (2) the tool accepts Stripe identifiers which could enable querying multiple businesses' data if an agent has access to external Stripe IDs, and…
From the tool's definition Tool name 'locations-deprecated' with description 'Get locations by stripeCustomerId or stripeSubscriptionId with companyId' indicates a retrieval operation that queries location data based on Stripe identifiers.
Documented attack patterns abuse exactly the kind of access locations-deprecated gives an agent:
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 locations-deprecated:
{
"version": "1",
"default": "deny",
"tools": {
"locations-deprecated": {}
}
}locations-deprecated is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get locations by stripeCustomerId or stripeSubscriptionId with companyId. 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 locations-deprecated: 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.
locations-deprecated 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 locations-deprecated 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 locations-deprecated. 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.
locations-deprecated is provided by the GoHighLevel MCP Server MCP server (drausal/gohighlevel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
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.
Free to start. No card required.
406 GoHighLevel MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.