Get custom fields for a location, optionally filtered by model type
AI agents call get_location_custom_fields 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 metadata about custom fields associated with a location in the GoHighLevel CRM. It performs a read-only query with no capability to modify, delete, or execute operations. The optional filtering parameter does not change the fundamental nature of the operation.
From the tool's definition Tool name is 'get_location_custom_fields' and description states 'Get custom fields for a location, optionally filtered by model type'.
Attacks that exploit this kind of access
Get custom fields for a location, optionally filtered by model type. 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 get_location_custom_fields: 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.
get_location_custom_fields 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_fields 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_fields. 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_fields is provided by the GoHighLevel MCP Server MCP server (keshigami/ghl-mcp-workiong). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →