ghl_create_store_setting

Create or update store settings including shipping origin and notifications

Server GoHighLevel MCP Server thinkbedo/gohighlevel_mcp
Category Write
Risk class Medium
Parameters 00 required

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 needs a policy

This tool modifies configuration data (store settings) but does not execute code, delete data, or move money. Store setting changes are reversible—they can be updated again or restored. While misuse could disrupt store operations (e.g., changing shipping origin to cause fulfillment issues), the impact is limited to configuration rather than data destruction or financial transactions.

From the tool's definition Tool description states 'Create or update store settings' which are reversible data modifications. The verb 'create or update' and the scope (store settings like shipping origin and notifications) indicate Write operations typical of CRM configuration.

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 GoHighLevel MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on ghl_create_store_setting? +

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.

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 GoHighLevel MCP Server MCP server (thinkbedo/gohighlevel_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

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.