create_location_custom_field
Create a new custom field for a location
This record as markdown: /tools/hooker-dev-hailey-mcp/create-location-custom-field.md
What create_location_custom_field does on GoHighLevel MCP Server
AI agents use create_location_custom_field to create or update resources in GoHighLevel MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GoHighLevel MCP Server environment.
Why create_location_custom_field is rated Medium
This tool creates (writes) a new custom field definition for a location within the CRM system. It is reversible—custom fields can be deleted or modified—and has no side effects beyond adding metadata to a location record. It does not delete data (Destructive), execute arbitrary code (Execute), involve financial transactions (Financial), or trigger external operations (Execute).
From the tool's definition Tool name 'create_location_custom_field' and description 'Create a new custom field for a location' indicate a creation operation that modifies location configuration data.
Attacks that exploit this kind of access
The rule that runs create_location_custom_field safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GoHighLevel MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_location_custom_field, this is the rule to start with:
create_location_custom_field stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect GoHighLevel MCP Server, apply this rule, and every create_location_custom_field call is checked against it from then on.
Questions about create_location_custom_field
Create a new custom field for a location. It is categorised as a Write tool in the GoHighLevel MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the GoHighLevel MCP Server MCP server in PolicyLayer and add a rule for create_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.
create_location_custom_field is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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 create_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.
create_location_custom_field is provided by the GoHighLevel MCP Server MCP server (hooker-dev/hailey-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.
This server
Across the catalogue