update_location_tag

Update an existing location tag

SERVERGhl SOURCEghl-mcp-server

Medium RISK CLASS

Category Write

Parameters 33 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What update_location_tag does on Ghl

AI agents use update_location_tag 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 for the tag
`tagId`	string	Yes	The tag ID to update
`locationId`	string	Yes	The location ID

Parameters from the server's own tool schema.

RISK

Why update_location_tag is rated Medium

This tool creates or modifies data reversibly by updating a location tag. It does not delete data (would be Destructive) or execute arbitrary code (would be Execute). The severity is medium because tag updates could affect contact visibility/organization in a CRM system, but the impact is limited in scope and reversible.

From the tool's definition Tool name 'update_location_tag' and description 'Update an existing location tag' indicate modification of existing data. The action is reversible (tags can be updated again or removed) rather than destructive.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

update_location_tag Rate-limited

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

FAQ

Questions about update_location_tag

What does the update_location_tag tool do? +

Update an existing location tag. 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_tag accept? +

update_location_tag accepts 3 parameters: name, tagId, locationId. Required: name, tagId, 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_tag? +

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

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

Can I rate-limit update_location_tag? +

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

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

update_location_tag 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

add-tag on Kanban MCP Server →aroflo_create_or_update_record on AroFlo MCP →kb_tag on Persistent Kb →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

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