get_location
Get detailed information about a specific location/sub-account by ID
This record as markdown: /tools/ghl/get-location.md
What get_location does on Ghl
AI agents call get_location 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 |
|---|---|---|---|
locationId | string | Yes | The unique ID of the location to retrieve |
Parameters from the server's own tool schema.
Why get_location is rated Low
This tool retrieves data about a location or sub-account without creating, modifying, deleting, or executing any actions. It is a straightforward read operation. No side effects are indicated. Severity is low because exposing location/account details carries minimal risk unless the data itself is highly sensitive, but the tool itself performs only a safe lookup.
From the tool's definition Tool name and description both indicate retrieval only: 'Get detailed information about a specific location/sub-account by ID'. The verb 'Get' and the phrase 'detailed information' signify a query operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_location 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 get_location, this is the rule to start with:
get_location 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 get_location call is checked against it from then on.
Questions about get_location
Get detailed information about a specific location/sub-account by ID. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
get_location accepts 1 parameter: locationId. Required: locationId. 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 get_location: 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.
get_location 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 get_location 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 get_location. 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.
get_location 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