This record as markdown: /tools/aiwerk-mcp-server-ghl/locations-update-custom-field.md
What locations_update_custom_field does on Ghl
AI agents use locations_update_custom_field to create or update resources in Ghl, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ghl environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | Custom Field Id |
name | string | Yes | |
model | string | — | Model of the custom field you want to update |
position | number | — | |
locationId | string | — | Location Id Defaults to GHL_LOCATION_ID when omitted. |
placeholder | string | — | |
acceptedFormat | array | — | |
isMultipleFile | boolean | — | |
maxNumberOfFiles | number | — | |
textBoxListOptions | array | — |
Parameters from the server's own tool schema.
Why locations_update_custom_field is rated Medium
An AI agent can call locations_update_custom_field faster than any human can review: one bad instruction and it creates or modifies resources in Ghl by the hundred, each call as confident as the last.
Risk signalsHigh parameter count (10 properties)
Attacks that exploit this kind of access
The rule that runs locations_update_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 locations_update_custom_field, this is the rule to start with:
locations_update_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 Ghl, apply this rule, and every locations_update_custom_field call is checked against it from then on.
Questions about locations_update_custom_field
Update Custom Field. It is categorised as a Write tool in the Ghl MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
locations_update_custom_field accepts 10 parameters: id, name, model, position, locationId, placeholder, acceptedFormat, isMultipleFile, maxNumberOfFiles, textBoxListOptions. Required: id, name. 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 locations_update_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.
locations_update_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 locations_update_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 locations_update_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.
locations_update_custom_field is provided by the Ghl MCP server (@aiwerk/mcp-server-ghl). 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