get-location

THE RISK

Low Risk

Why get-location needs a policy

This tool retrieves and returns details about a sub-account based on its ID. It is a read-only operation with no side effects, no data modification, no destructive actions, and no financial impact. The blast radius of misuse is minimal—exposure of sub-account details. Therefore, it is classified as Read with low severity.

From the tool's definition Tool name 'get-location' and description 'Get details of a Sub-Account (Formerly Location) by passing the sub-account id' indicate a retrieval operation that queries sub-account information without modifying data.

Documented attack patterns abuse exactly the kind of access get-location gives an agent:

POLICY

How to control get-location

PolicyLayer is an MCP gateway — it sits between your AI agents and GoHighLevel MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get-location:

policy.json

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

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

Create a free account and register GoHighLevel MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More GoHighLevel MCP Server tools

Financial charge Create a new wallet charge Financial send-invoice API to send invoice by invoice id Financial record-invoice API to record manual payment for an invoice by invoice id Financial record-order-payment The Financial auto-payment-invoice-schedule API to manage auto payment for a schedule Financial generate-payment-link Update SaaS subscription for given locationId and customerId Financial update-saas-subscription-deprecated Update SaaS subscription for given locationId and customerId Destructive bulk-delete-media-objects Soft-deletes or trashes multiple files and folders in a single request

All 406 GoHighLevel MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get-location

What does the get-location tool do? +

Get details of a Sub-Account (Formerly Location) by passing the sub-account id. 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? +

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

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

Can I rate-limit get-location? +

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

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

get-location 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.

Enforce policy on every GoHighLevel MCP Server tool call.

Start from GoHighLevel MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →