ghl_create_shipping_rate
Create a new shipping rate for a shipping zone
This record as markdown: /tools/ghl/ghl-create-shipping-rate.md
What ghl_create_shipping_rate does on Ghl
AI agents use ghl_create_shipping_rate 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 | Yes | Name of the shipping rate |
amount | number | Yes | Shipping rate amount |
currency | string | Yes | Currency code (e.g., USD) |
locationId | string | — | GHL Location ID (optional, uses default if not provided) |
conditionType | string | Yes | Condition type for rate calculation |
shippingZoneId | string | Yes | ID of the shipping zone |
Parameters from the server's own tool schema.
Why ghl_create_shipping_rate is rated Medium
This tool creates new shipping rate records, which is a reversible data modification operation. It does not delete, destroy, or execute arbitrary code. While it affects e-commerce configuration, the severity is low because shipping rate misuse has limited blast radius compared to financial transactions or customer data deletion. The operation is reversible (rates can be updated or deleted afterward).
From the tool's definition Tool name 'create_shipping_rate' indicates creation of a new resource (shipping rate). Description states 'Create a new shipping rate for a shipping zone', which is a reversible write operation that adds configuration data.
Attacks that exploit this kind of access
The rule that runs ghl_create_shipping_rate 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_create_shipping_rate, this is the rule to start with:
ghl_create_shipping_rate 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_create_shipping_rate call is checked against it from then on.
Questions about ghl_create_shipping_rate
Create a new shipping rate for a shipping zone. 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_create_shipping_rate accepts 6 parameters: name, amount, currency, locationId, conditionType, shippingZoneId. Required: name, amount, currency, conditionType, 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_create_shipping_rate: 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_create_shipping_rate 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_create_shipping_rate 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_create_shipping_rate. 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_create_shipping_rate 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