This record as markdown: /tools/ghl/ghl-get-store-setting.md
What ghl_get_store_setting does on Ghl
AI agents call ghl_get_store_setting to retrieve information from Ghl without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
locationId | string | — | GHL Location ID (optional, uses default if not provided) |
Parameters from the server's own tool schema.
Why ghl_get_store_setting is rated Low
This is a read-only operation that queries existing store settings. It has no capacity to modify, delete, or execute actions. The blast radius of misuse is minimal since it only exposes configuration information.
From the tool's definition Tool name contains 'get' and description states 'Get current store settings' — retrieves configuration data with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs ghl_get_store_setting safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ghl, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ghl_get_store_setting, this is the rule to start with:
ghl_get_store_setting is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Ghl, apply this rule, and every ghl_get_store_setting call is checked against it from then on.
Questions about ghl_get_store_setting
Get current store settings. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
ghl_get_store_setting accepts 1 parameter: locationId. The full parameter table on this page comes from the server's own tool schema.
Register the Ghl 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 Ghl. Nothing to install.
ghl_get_store_setting is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
ghl_get_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
Across the catalogue