get-location-tags

Get Sub-Account (Formerly Location) Tags

SERVERGoHighLevel MCP Server SOURCEdrausal/gohighlevel-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/drausal-gohighlevel-mcp/get-location-tags.md

WHAT IT DOES

What get-location-tags does on GoHighLevel MCP Server

AI agents call get-location-tags to retrieve information from GoHighLevel MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get-location-tags is rated Low

This tool retrieves tag data associated with a location/sub-account in GoHighLevel. It queries existing data without creating, modifying, deleting, or executing any external operations. The blast radius of misuse is minimal—an unauthorized read of tag metadata poses low risk compared to write, execute, or destructive operations.

From the tool's definition Tool name 'get-location-tags' and description 'Get Sub-Account (Formerly Location) Tags' indicate a retrieval operation. The verb 'Get' and lack of any modification language confirm this is a read-only query.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get-location-tags safely

PolicyLayer is an MCP gateway: it sits between your AI agents and GoHighLevel MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get-location-tags, this is the rule to start with:

get-location-tags Allowed

get-location-tags is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get-location-tags": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect GoHighLevel MCP Server, apply this rule, and every get-location-tags call is checked against it from then on.

FAQ

Questions about get-location-tags

What does the get-location-tags tool do? +

Get Sub-Account (Formerly Location) Tags. It is categorised as a Read tool in the GoHighLevel MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get-location-tags? +

Register the GoHighLevel MCP Server MCP server in PolicyLayer and add a rule for get-location-tags: 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 get-location-tags? +

get-location-tags is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get-location-tags? +

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

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

get-location-tags is provided by the GoHighLevel MCP Server MCP server (drausal/gohighlevel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

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

This server

All 406 GoHighLevel MCP Server tools →

Across the catalogue

get_cocktail_by_tags on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →