This record as markdown: /tools/ghl/ghl-list-shipping-zones.md
What ghl_list_shipping_zones does on Ghl
AI agents call ghl_list_shipping_zones 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 |
|---|---|---|---|
limit | number | — | Number of zones to return (optional) |
offset | number | — | Number of zones to skip (optional) |
locationId | string | — | GHL Location ID (optional, uses default if not provided) |
withShippingRate | boolean | — | Include shipping rates in response (optional) |
Parameters from the server's own tool schema.
Why ghl_list_shipping_zones is rated Low
This tool retrieves and displays shipping zone information for a location. It has no side effects, does not modify, delete, or execute any operations. The blast radius of misuse is minimal—an agent could only retrieve zone data, which does not expose sensitive business logic or enable harmful actions on the GoHighLevel platform.
From the tool's definition 'List all shipping zones for a location' — the verb 'list' and the retrieval nature indicate a read-only operation that queries existing data without modification.
Attacks that exploit this kind of access
The rule that runs ghl_list_shipping_zones 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 ghl_list_shipping_zones, this is the rule to start with:
ghl_list_shipping_zones is read-only, so it stays allowed. 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 ghl_list_shipping_zones call is checked against it from then on.
Questions about ghl_list_shipping_zones
List all shipping zones for a location. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
ghl_list_shipping_zones accepts 4 parameters: limit, offset, locationId, withShippingRate. 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 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 Ghl. 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 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