get_location_custom_field

Get a specific custom field by ID

SERVERGoHighLevel MCP Server SOURCEhridayshah7/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/hridayshah7-gohighlevel-mcp/get-location-custom-field.md

What get_location_custom_field does on GoHighLevel MCP Server

AI agents call get_location_custom_field 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.

Why get_location_custom_field is rated Low

This tool retrieves (gets) a single custom field by ID from a location in the GoHighLevel CRM. It performs a query operation without modifying, deleting, or executing any data. The 'get' verb and read-only nature of the operation clearly place it in the Read category. Severity is low because retrieving a custom field definition poses minimal risk even if misused by an AI agent.

From the tool's definition Tool name 'get_location_custom_field' and description 'Get a specific custom field by ID' indicate a retrieval operation with no side effects.

Questions about get_location_custom_field

What does the get_location_custom_field tool do? +

Get a specific custom field by ID. 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 get_location_custom_field? +

Register the GoHighLevel MCP Server 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 GoHighLevel MCP Server. Nothing to install.

What risk level is get_location_custom_field? +

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

Can I rate-limit get_location_custom_field? +

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.

How do I block get_location_custom_field completely? +

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.

What MCP server provides get_location_custom_field? +

get_location_custom_field is provided by the GoHighLevel MCP Server MCP server (hridayshah7/gohighlevel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of GoHighLevel MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.