List all shipping zones for a location
AI agents call ghl_list_shipping_zones to retrieve information from GoHighLevel MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays existing shipping zone configuration data. It performs no write, delete, execution, or financial operations. The blast radius of misuse is minimal — an attacker gains only visibility into shipping logistics metadata, which does not directly compromise customer data, enable fraud, or cause operational damage.
From the tool's definition Tool name contains 'list' and description states 'List all shipping zones for a location' — a query operation that retrieves data without modification or side effects.
Attacks that exploit this kind of access
List all shipping zones for a location. It is categorised as a Read tool in the GoHighLevel MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GoHighLevel MCP Server MCP server in PolicyLayer and add a rule for ghl_list_shipping_zones: 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.
ghl_list_shipping_zones is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the ghl_list_shipping_zones 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 ghl_list_shipping_zones. 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.
ghl_list_shipping_zones is provided by the GoHighLevel MCP Server MCP server (keshigami/ghl-mcp-workiong). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →