This record as markdown: /tools/aiwerk-mcp-server-ghl/store-create-store-setting.md
What store_create_store_setting does on Ghl
AI agents use store_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 |
|---|---|---|---|
altId | string | — | Location Id or Agency Id Defaults to GHL_LOCATION_ID when omitted. |
altType | string | — | Defaults to GHL_LOCATION_ID when omitted. |
shippingOrigin | object | Yes | Shipping origin address |
storeOrderNotification | object | — | Store order notification email |
storeOrderFulfillmentNotification | object | — | Store order fulfillment notification email |
Parameters from the server's own tool schema.
Why store_create_store_setting is rated Medium
An AI agent can call store_create_store_setting 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 (22 properties)
Attacks that exploit this kind of access
The rule that runs store_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 store_create_store_setting, this is the rule to start with:
store_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 store_create_store_setting call is checked against it from then on.
Questions about store_create_store_setting
Create/Update Store Settings. 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.
store_create_store_setting accepts 5 parameters: altId, altType, shippingOrigin, storeOrderNotification, storeOrderFulfillmentNotification. 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 store_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.
store_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 store_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 store_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.
store_create_store_setting 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.
More on Ghl, and thousands of servers like it.
This server
Across the catalogue