This record as markdown: /tools/ghl/create-location-tag.md
What create_location_tag does on Ghl
AI agents use create_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 | Name of the tag to create |
locationId | string | Yes | The location ID to create tag in |
Parameters from the server's own tool schema.
Why create_location_tag is rated Medium
This tool creates a new tag (metadata/label), which is a reversible write operation. Tags can be deleted or renamed if needed. The blast radius is minimal—miscreating a tag causes no harm to existing data or business operations. The sibling tools on this server (add_contact_followers, add_contact_tags, bulk_update_contact_tags) confirm that tag management is a routine data modification function on GoHighLevel.
From the tool's definition Tool name 'create_location_tag' and description 'Create a new tag for a location' indicate data creation. The verb 'create' combined with 'tag' describes adding a new metadata object to a location resource.
Attacks that exploit this kind of access
The rule that runs create_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 create_location_tag, this is the rule to start with:
create_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Ghl, apply this rule, and every create_location_tag call is checked against it from then on.
Questions about create_location_tag
Create a new tag for a location. 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.
create_location_tag accepts 2 parameters: name, locationId. Required: name, locationId. The full parameter table on this page comes from the server's own tool schema.
Register the Ghl MCP server in PolicyLayer and add a rule for create_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.
create_location_tag is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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.
Set action: deny in the PolicyLayer policy for create_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.
create_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.
More on Ghl, and thousands of servers like it.
This server
Across the catalogue