ghl_create_store_setting

Create or update store settings including shipping origin and notifications

SERVERGhl SOURCEghl-mcp-server
Medium RISK CLASS
Category Write
Parameters 21 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

ParameterTypeRequiredDescription
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).

Questions about ghl_create_store_setting

What does the ghl_create_store_setting tool do? +

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.

What parameters does ghl_create_store_setting accept? +

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.

How do I enforce a policy on ghl_create_store_setting? +

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.

What risk level is ghl_create_store_setting? +

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

Can I rate-limit ghl_create_store_setting? +

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.

How do I block ghl_create_store_setting completely? +

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.

What MCP server provides ghl_create_store_setting? +

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Ghl's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.