ghl_create_shipping_carrier
Create a new shipping carrier for dynamic rate calculation
This record as markdown: /tools/ghl/ghl-create-shipping-carrier.md
What ghl_create_shipping_carrier does on Ghl
AI agents use ghl_create_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 |
|---|---|---|---|
name | string | Yes | Name of the shipping carrier |
services | array | Yes | Array of available services |
locationId | string | — | GHL Location ID (optional, uses default if not provided) |
callbackUrl | string | Yes | Callback URL for carrier rate requests |
Parameters from the server's own tool schema.
Why ghl_create_shipping_carrier is rated Medium
This tool creates a new shipping carrier entry, which is reversible (can be updated or deleted). It does not execute arbitrary code, delete data permanently, move money, or trigger external operations. It belongs to the Write category as a data creation action. The impact is limited to adding a configuration option for shipping calculations, making it low severity.
From the tool's definition Tool name "create_shipping_carrier" and description "Create a new shipping carrier for dynamic rate calculation" indicate creation of new data (configuration/settings entry) without destructive deletion or code execution.
Attacks that exploit this kind of access
The rule that runs ghl_create_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_create_shipping_carrier, this is the rule to start with:
ghl_create_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_create_shipping_carrier call is checked against it from then on.
Questions about ghl_create_shipping_carrier
Create a new shipping carrier for dynamic rate calculation. 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_carrier accepts 4 parameters: name, services, locationId, callbackUrl. Required: name, services, callbackUrl. 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_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_create_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_create_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_create_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_create_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