ghl_create_store_setting
Create or update store settings including shipping origin and notifications
This record as markdown: /tools/ghl/ghl-create-store-setting.md
What ghl_create_store_setting does on Ghl
AI agents use ghl_create_store_setting 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) |
shippingOrigin | object | Yes | Shipping origin address details |
Parameters from the server's own tool schema.
Why ghl_create_store_setting is rated Medium
This tool modifies store configuration data (shipping origin, notification settings) but does not delete, overwrite irreversibly, execute arbitrary code, or commit financial transactions. Changes can be reverted by updating settings again. Classified as Write rather than Read (it changes state) or more severe categories (it is not destructive or financial).
From the tool's definition Tool description states 'Create or update store settings' — these are reversible configuration changes to a store's operational parameters (shipping origin, notifications).
Attacks that exploit this kind of access
The rule that runs ghl_create_store_setting 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_store_setting, this is the rule to start with:
ghl_create_store_setting 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_store_setting call is checked against it from then on.
Questions about ghl_create_store_setting
Create or update store settings including shipping origin and notifications. 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_store_setting accepts 2 parameters: locationId, shippingOrigin. Required: shippingOrigin. 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_store_setting: 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_store_setting 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_store_setting 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_store_setting. 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_store_setting 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