This record as markdown: /tools/ghl/get-location-custom-field.md
What get_location_custom_field does on Ghl
AI agents call get_location_custom_field 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 |
customFieldId | string | Yes | The custom field ID to retrieve |
Parameters from the server's own tool schema.
Why get_location_custom_field is rated Low
This tool retrieves or queries a custom field value. It performs a read-only operation with no side effects, no data modification, and no irreversible actions. The low severity reflects minimal blast radius if misused by an AI agent — at worst, unauthorized data access of a single field.
From the tool's definition Tool name and description: 'Get a specific custom field by ID' — the verb 'Get' and 'by ID' indicate retrieval of data without modification or execution.
Attacks that exploit this kind of access
The rule that runs get_location_custom_field 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_field, this is the rule to start with:
get_location_custom_field 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_field call is checked against it from then on.
Questions about get_location_custom_field
Get a specific custom field by ID. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
get_location_custom_field accepts 2 parameters: locationId, customFieldId. Required: locationId, customFieldId. 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_field: 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_field 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_field 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_field. 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_field 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