get_location_tag

Get a specific location tag by ID

SERVERGhl SOURCEghl-mcp-server

Low RISK CLASS

Category Read

Parameters 22 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What get_location_tag does on Ghl

AI agents call get_location_tag to retrieve information from Ghl without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`tagId`	string	Yes	The tag ID to retrieve
`locationId`	string	Yes	The location ID

Parameters from the server's own tool schema.

RISK

Why get_location_tag is rated Low

This tool retrieves or queries data (a location tag by its ID) without modifying, deleting, or executing any external operations. It is a straightforward read-only query operation, making it the least risky category.

From the tool's definition Tool name 'get_location_tag' and description 'Get a specific location tag by ID' indicate a retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_location_tag Allowed

get_location_tag 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_tag": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect Ghl, apply this rule, and every get_location_tag call is checked against it from then on.

FAQ

Questions about get_location_tag

What does the get_location_tag tool do? +

Get a specific location tag by ID. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.

What parameters does get_location_tag accept? +

get_location_tag accepts 2 parameters: tagId, locationId. Required: tagId, locationId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_location_tag? +

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

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

Can I rate-limit get_location_tag? +

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

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

get_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

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