update_location_custom_field

Update an existing custom field

SERVERGhl SOURCEghl-mcp-server

Medium RISK CLASS

Category Write

Parameters 53 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What update_location_custom_field does on Ghl

AI agents use update_location_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
`name`	string	Yes	Updated name of the custom field
`position`	number	—	Updated position/order
`locationId`	string	Yes	The location ID
`placeholder`	string	—	Updated placeholder text
`customFieldId`	string	Yes	The custom field ID to update

Parameters from the server's own tool schema.

RISK

Why update_location_custom_field is rated Medium

This tool creates or modifies data (a custom field value) in a reversible manner. It does not delete, execute arbitrary code, move money, or trigger external operations. The severity is medium because custom field updates in a CRM can affect business logic, workflows, or reporting, but the change is reversible and localized to a single field.

From the tool's definition Tool name contains 'update' and description states 'Update an existing custom field' — modifies data reversibly without deletion or destruction.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

update_location_custom_field Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_location_custom_field": {
      "limits": [
        {
          "counter": "update_location_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 update_location_custom_field call is checked against it from then on.

FAQ

Questions about update_location_custom_field

What does the update_location_custom_field tool do? +

Update an existing 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.

What parameters does update_location_custom_field accept? +

update_location_custom_field accepts 5 parameters: name, position, locationId, placeholder, customFieldId. Required: name, locationId, customFieldId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_location_custom_field? +

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

What risk level is update_location_custom_field? +

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

Can I rate-limit update_location_custom_field? +

Yes. Add a rate_limit block to the update_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 update_location_custom_field completely? +

Set action: deny in the PolicyLayer policy for update_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 update_location_custom_field? +

update_location_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 →