This record as markdown: /tools/ghl/ghl-update-shipping-zone.md
What ghl_update_shipping_zone does on Ghl
AI agents use ghl_update_shipping_zone to create or update resources in Ghl, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ghl environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | — | New name for the shipping zone (optional) |
countries | array | — | Updated array of countries with optional state restrictions (optional) |
locationId | string | — | GHL Location ID (optional, uses default if not provided) |
shippingZoneId | string | Yes | ID of the shipping zone to update |
Parameters from the server's own tool schema.
Why ghl_update_shipping_zone is rated Medium
The tool modifies shipping zone configuration (name and/or countries list) but does not delete or irreversibly destroy the zone itself. This is a reversible change to business settings. Severity is medium because misuse could disrupt shipping operations and affect customer orders, but the impact is limited to a specific zone configuration and can be undone by updating again.
From the tool's definition Tool name contains 'update' and description states 'Update a shipping zone's name or countries' - indicates modification of existing configuration data.
Risk signalsAccepts freeform code/query input (countries[].code)
Attacks that exploit this kind of access
The rule that runs ghl_update_shipping_zone 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_update_shipping_zone, this is the rule to start with:
ghl_update_shipping_zone stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_update_shipping_zone call is checked against it from then on.
Questions about ghl_update_shipping_zone
Update a shipping zone's name or countries. It is categorised as a Write tool in the Ghl MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
ghl_update_shipping_zone accepts 4 parameters: name, countries, locationId, shippingZoneId. Required: shippingZoneId. 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_update_shipping_zone: 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_update_shipping_zone is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the ghl_update_shipping_zone 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_update_shipping_zone. 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_update_shipping_zone 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