ghl_create_store_setting
Create or update store settings including shipping origin and notifications
This record as markdown: /tools/hridayshah7-gohighlevel-mcp/ghl-create-store-setting.md
What ghl_create_store_setting does on GoHighLevel MCP Server
AI agents use ghl_create_store_setting to create or update resources in GoHighLevel MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GoHighLevel MCP Server environment.
Why ghl_create_store_setting is rated Medium
This tool creates or updates e-commerce store settings (shipping origin, notifications). These are reversible modifications to data configuration, fitting the Write category. Severity is medium because misconfiguration could disrupt order fulfillment or customer communications, but the changes are not destructive and do not move money directly.
From the tool's definition Tool description states 'Create or update store settings' — both create and update operations are write operations that modify data reversibly. The function name 'ghl_create_store_setting' and description explicitly indicate mutation of configuration data.
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 GoHighLevel MCP Server, 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 GoHighLevel MCP Server, 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 GoHighLevel MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the GoHighLevel MCP Server 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 GoHighLevel MCP Server. 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 GoHighLevel MCP Server MCP server (hridayshah7/gohighlevel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GoHighLevel MCP Server, and thousands of servers like it.
This server
Across the catalogue