update_location

Update an existing sub-account/location in GoHighLevel

SERVERGhl SOURCEghl-mcp-server

Medium RISK CLASS

Category Write

Parameters 112 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What update_location does on Ghl

AI agents use update_location 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
`city`	string	—	Updated city
`name`	string	—	Updated name of the sub-account/location
`phone`	string	—	Updated phone number
`state`	string	—	Updated state
`address`	string	—	Updated business address
`country`	string	—	Updated 2-letter country code
`website`	string	—	Updated website URL
`timezone`	string	—	Updated timezone
`companyId`	string	Yes	Company/Agency ID
`locationId`	string	Yes	The unique ID of the location to update
`postalCode`	string	—	Updated postal/ZIP code

Parameters from the server's own tool schema.

RISK

Why update_location is rated Medium

This tool modifies existing location/sub-account records in GoHighLevel, which is a reversible write operation. It does not delete data (would be Destructive), execute code (would be Execute), move money (would be Financial), or merely read data (would be Read).

From the tool's definition Tool name is 'update_location' and description states 'Update an existing sub-account/location in GoHighLevel'. The verb 'update' indicates modification of existing data.

Risk signalsHigh parameter count (11 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

update_location Rate-limited

update_location 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": {
      "limits": [
        {
          "counter": "update_location_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 call is checked against it from then on.

FAQ

Questions about update_location

What does the update_location tool do? +

Update an existing sub-account/location in GoHighLevel. 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 accept? +

update_location accepts 11 parameters: city, name, phone, state, address, country, website, timezone, companyId, locationId, postalCode. Required: companyId, locationId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_location? +

Register the Ghl MCP server in PolicyLayer and add a rule for update_location: 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? +

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

Can I rate-limit update_location? +

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

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

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