This record as markdown: /tools/ghl/ghl-update-shipping-carrier.md
What ghl_update_shipping_carrier does on Ghl
AI agents use ghl_update_shipping_carrier 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 |
|---|---|---|---|
locationId | string | — | GHL Location ID (optional, uses default if not provided) |
shippingCarrierId | string | Yes | ID of the shipping carrier to update |
Parameters from the server's own tool schema.
Why ghl_update_shipping_carrier is rated Medium
This tool modifies shipping carrier configuration/properties, which is a reversible write operation. It has medium severity due to potential disruption to fulfillment operations if updated incorrectly, but is not destructive (no deletion), financial (no money movement), or executable (no code/command execution).
From the tool's definition Tool name 'ghl_update_shipping_carrier' and description 'Update a shipping carrier's properties' indicate modification of existing data without deletion or financial commitment.
Attacks that exploit this kind of access
The rule that runs ghl_update_shipping_carrier 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_carrier, this is the rule to start with:
ghl_update_shipping_carrier 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_carrier call is checked against it from then on.
Questions about ghl_update_shipping_carrier
Update a shipping carrier's properties. 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_carrier accepts 2 parameters: locationId, shippingCarrierId. Required: shippingCarrierId. 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_carrier: 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_carrier 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_carrier 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_carrier. 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_carrier 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