ghl_update_custom_field

Update an existing custom field by ID. Can modify name, description, options, and other properties.

SERVERGhl SOURCEghl-mcp-server

Medium RISK CLASS

Category Write

Parameters 91 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ghl/ghl-update-custom-field.md

WHAT IT DOES

What ghl_update_custom_field does on Ghl

AI agents use ghl_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	The ID of the custom field to update
`name`	string	—	Updated field name
`options`	array	—	Updated options (replaces all existing options - include all options you want to keep)
`locationId`	string	—	GoHighLevel location ID (will use default if not provided)
`description`	string	—	Updated description of the field
`placeholder`	string	—	Updated placeholder text for the field
`showInForms`	boolean	—	Whether the field should be shown in forms
`maxFileLimit`	number	—	Updated maximum file limit for uploads
`acceptedFormats`	string	—	Updated allowed file formats for uploads

Parameters from the server's own tool schema.

RISK

Why ghl_update_custom_field is rated Medium

This tool modifies existing custom field metadata within the GoHighLevel CRM system. While reversible (updates can be corrected), it affects data structure and field configurations. Updates to custom fields could impact workflows, reporting, and contact data handling if misconfigured by an AI agent. The blast radius is moderate—localized to field definitions rather than mass data deletion or financial transactions.

From the tool's definition Tool description states 'Update an existing custom field by ID. Can modify name, description, options, and other properties.' The verb 'Update' and modification of multiple field properties (name, description, options) clearly indicates write operations that…

Risk signalsAccepts URL/endpoint input (options[].url) · High parameter count (12 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs ghl_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 ghl_update_custom_field, this is the rule to start with:

ghl_update_custom_field Rate-limited

ghl_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ghl_update_custom_field": {
      "limits": [
        {
          "counter": "ghl_update_custom_field_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Ghl, apply this rule, and every ghl_update_custom_field call is checked against it from then on.

FAQ

Questions about ghl_update_custom_field

What does the ghl_update_custom_field tool do? +

Update an existing custom field by ID. Can modify name, description, options, and other properties. 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.

What parameters does ghl_update_custom_field accept? +

ghl_update_custom_field accepts 9 parameters: id, name, options, locationId, description, placeholder, showInForms, maxFileLimit, acceptedFormats. Required: id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on ghl_update_custom_field? +

Register the Ghl MCP server in PolicyLayer and add a rule for ghl_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.

What risk level is ghl_update_custom_field? +

ghl_update_custom_field is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit ghl_update_custom_field? +

Yes. Add a rate_limit block to the ghl_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.

How do I block ghl_update_custom_field completely? +

Set action: deny in the PolicyLayer policy for ghl_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.

What MCP server provides ghl_update_custom_field? +

ghl_update_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.

KEEP EXPLORING

More on Ghl, and thousands of servers like it.

This server

All 253 Ghl tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →