Low Risk

ghl_get_store_setting

Get current store settings

How to control ghl_get_store_setting ↓

AI agents call ghl_get_store_setting to retrieve information from GoHighLevel MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool queries and retrieves store configuration data without creating, modifying, deleting, or executing operations. It is a passive read-only operation consistent with the Read category. Severity is low because retrieving settings poses minimal risk even if misused by an AI agent, as it only exposes configuration information without enabling destructive actions.

From the tool's definition Tool name 'ghl_get_store_setting' and description 'Get current store settings' indicate a retrieval operation with no modification or side effects.

Documented attack patterns abuse exactly the kind of access ghl_get_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 ghl_get_store_setting:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "ghl_get_store_setting": {}
  }
}

ghl_get_store_setting is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register GoHighLevel MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the ghl_get_store_setting tool do? +

Get current store settings. It is categorised as a Read tool in the GoHighLevel MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on ghl_get_store_setting? +

Register the GoHighLevel MCP Server MCP server in PolicyLayer and add a rule for ghl_get_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_get_store_setting? +

ghl_get_store_setting is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit ghl_get_store_setting? +

Yes. Add a rate_limit block to the ghl_get_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_get_store_setting completely? +

Set action: deny in the PolicyLayer policy for ghl_get_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_get_store_setting? +

ghl_get_store_setting is provided by the GoHighLevel MCP Server MCP server (mastanley13/gohighlevel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every GoHighLevel MCP Server tool call.

Deterministic rules across all 255 GoHighLevel MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

255 GoHighLevel MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.