locations

Get locations by stripeCustomerId or stripeSubscriptionId with companyId

SERVERGoHighLevel MCP Server SOURCEdrausal/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/drausal-gohighlevel-mcp/locations.md

WHAT IT DOES

What locations does on GoHighLevel MCP Server

AI agents call 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 locations is rated Low

This tool retrieves location information based on billing/subscription identifiers. It performs a read-only query with no side effects, no code execution, no data modification, and no financial operations. The low severity reflects that exposure of location metadata poses minimal risk compared to write, destructive, or financial operations.

From the tool's definition Tool name 'locations' and description 'Get locations by stripeCustomerId or stripeSubscriptionId with companyId' indicates a retrieval operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

locations Allowed

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": {
    "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 locations call is checked against it from then on.

FAQ

Questions about locations

What does the locations tool do? +

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.

How do I enforce a policy on locations? +

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

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

Can I rate-limit locations? +

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

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

locations 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.

KEEP EXPLORING

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

This server

All 406 GoHighLevel MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

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