Create or update store settings by altId and altType.
AI agents use 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.
The tool creates or updates store settings without permanent deletion, classifying it as Write rather than Destructive. Settings can typically be changed or reverted. Severity is medium because misconfiguration of store settings could disrupt business operations, affect customer-facing systems, or expose configuration details, but the changes are not irreversible and the impact depends on which settings are modified.
From the tool's definition Tool name and description explicitly indicate 'Create or update store settings' - these are reversible write operations that modify data.
Documented attack patterns abuse exactly the kind of access create-store-setting gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and GoHighLevel MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create-store-setting:
{
"version": "1",
"default": "deny",
"tools": {
"create-store-setting": {
"limits": [
{
"counter": "create-store-setting_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
Create or update store settings by altId and altType. 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 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.
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 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 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.
create-store-setting is provided by the GoHighLevel MCP Server MCP server (drausal/gohighlevel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from GoHighLevel MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
406 GoHighLevel MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.