update_location_custom_field · GoHighLevel MCP Server MCP

WHAT IT DOES

What update_location_custom_field does on GoHighLevel MCP Server

AI agents use update_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 IT NEEDS A POLICY

Why update_location_custom_field needs a policy

This tool modifies existing custom field data within a GoHighLevel location/sub-account. Updates are reversible—a previous value can be restored by updating again. It does not delete data (would be Destructive), execute arbitrary code (would be Execute), handle financial transactions (would be Financial), or merely read data (would be Read).

From the tool's definition Tool name 'update_location_custom_field' and description 'Update an existing custom field' indicate modification of data. The verb 'update' confirms reversible data mutation rather than deletion or read-only access.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

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.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches GoHighLevel MCP Server, so you can run agents against it safely.

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 GoHighLevel MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_location_custom_field? +

Register the GoHighLevel MCP Server 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 GoHighLevel MCP Server. 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 GoHighLevel MCP Server MCP server (thinkbedo/gohighlevel_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.