store_update_shipping_rate

Update Shipping Rate

SERVERGhl SOURCE@aiwerk/mcp-server-ghl

Medium RISK CLASS

Category Write

Parameters 122 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aiwerk-mcp-server-ghl/store-update-shipping-rate.md

WHAT IT DOES

What store_update_shipping_rate does on Ghl

AI agents use store_update_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	—	Name of the shipping zone
`altId`	string	—	Location Id or Agency Id Defaults to GHL_LOCATION_ID when omitted.
`amount`	number	—	The amount of the shipping rate if it is normal rate (0 means free ). Fixed Handling fee if it is a carrier rate (it will add to the carrier rate).
`altType`	string	—	Defaults to GHL_LOCATION_ID when omitted.
`currency`	string	—	The currency of the amount of the rate / handling fee
`description`	string	—	Delivery description
`maxCondition`	number	—	Maximum condition for applying this price. set 0 or null if there is no maximum
`minCondition`	number	—	Minimum condition for applying this price. set 0 or null if there is no minimum
`conditionType`	string	—	Type of condition to provide the conditional pricing
`isCarrierRate`	boolean	—	is this a carrier rate
`shippingRateId`	string	Yes	ID of the shipping rate that needs to be returned
`shippingZoneId`	string	Yes	ID of the shipping zone

Parameters from the server's own tool schema.

RISK

Why store_update_shipping_rate is rated Medium

An AI agent can call store_update_shipping_rate faster than any human can review: one bad instruction and it creates or modifies resources in Ghl by the hundred, each call as confident as the last.

Risk signalsHigh parameter count (15 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs store_update_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 store_update_shipping_rate, this is the rule to start with:

store_update_shipping_rate Rate-limited

store_update_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "store_update_shipping_rate": {
      "limits": [
        {
          "counter": "store_update_shipping_rate_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Ghl, apply this rule, and every store_update_shipping_rate call is checked against it from then on.

FAQ

Questions about store_update_shipping_rate

What does the store_update_shipping_rate tool do? +

Update Shipping Rate. 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.

What parameters does store_update_shipping_rate accept? +

store_update_shipping_rate accepts 12 parameters: name, altId, amount, altType, currency, description, maxCondition, minCondition, conditionType, isCarrierRate, shippingRateId, shippingZoneId. Required: shippingRateId, shippingZoneId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on store_update_shipping_rate? +

Register the Ghl MCP server in PolicyLayer and add a rule for store_update_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.

What risk level is store_update_shipping_rate? +

store_update_shipping_rate is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit store_update_shipping_rate? +

Yes. Add a rate_limit block to the store_update_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.

How do I block store_update_shipping_rate completely? +

Set action: deny in the PolicyLayer policy for store_update_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.

What MCP server provides store_update_shipping_rate? +

store_update_shipping_rate is provided by the Ghl MCP server (@aiwerk/mcp-server-ghl). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Ghl, and thousands of servers like it.

This server

All 569 Ghl tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →