This record as markdown: /tools/ghl/get-location-custom-values.md
What get_location_custom_values does on Ghl
AI agents call get_location_custom_values 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 location ID |
Parameters from the server's own tool schema.
Why get_location_custom_values is rated Low
This tool retrieves configuration data (custom values) associated with a location in the GoHighLevel CRM system. It performs a read-only query with no ability to modify, delete, or execute operations. The blast radius is minimal—exposure would allow unauthorized viewing of location settings but cannot change state or trigger actions.
From the tool's definition Tool name 'get_location_custom_values' and description 'Get all custom values for a location' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_location_custom_values 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_custom_values, this is the rule to start with:
get_location_custom_values 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_custom_values call is checked against it from then on.
Questions about get_location_custom_values
Get all custom values for a location. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
get_location_custom_values 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_custom_values: 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_custom_values 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_custom_values 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_custom_values. 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_custom_values 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