update_location_tag

Update an existing location tag

SERVERGoHighLevel MCP Server SOURCEhooker-dev/hailey-mcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/hooker-dev-hailey-mcp/update-location-tag.md

What update_location_tag does on GoHighLevel MCP Server

AI agents use update_location_tag 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 update_location_tag is rated Medium

This tool creates or modifies data reversibly within the CRM system. While it alters stored configuration (location tags), the change is not destructive—it can be reverted by updating again to a previous value. The blast radius is contained to tag metadata management, affecting potentially filtered contact lists or workflow routing, making it Write severity medium rather than high.

From the tool's definition Tool name 'update_location_tag' and description 'Update an existing location tag' indicate modification of existing data (location tag records in GoHighLevel CRM). The verb 'update' is characteristic of reversible write operations.

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 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_tag? +

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

More on GoHighLevel MCP Server, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of GoHighLevel MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.