get-product-store-stats
API to fetch the total number of products, included in the store, and excluded from the store and other stats
This record as markdown: /tools/drausal-gohighlevel-mcp/get-product-store-stats.md
What get-product-store-stats does on GoHighLevel MCP Server
AI agents call get-product-store-stats to retrieve information from GoHighLevel MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get-product-store-stats is rated Low
This tool only retrieves and queries product store statistics (product counts, inclusion/exclusion status, and other metrics). It has no side effects, cannot modify data, execute code, delete records, or commit financial transactions. It is a straightforward data retrieval operation, making it a Read category tool with low severity risk.
From the tool's definition Tool description states it 'fetch[es]' statistics about products - a retrieval operation with no modification, deletion, or execution capability. The verb 'fetch' combined with 'stats' indicates a read-only data query.
Attacks that exploit this kind of access
The rule that runs get-product-store-stats 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 get-product-store-stats, this is the rule to start with:
get-product-store-stats 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 GoHighLevel MCP Server, apply this rule, and every get-product-store-stats call is checked against it from then on.
Questions about get-product-store-stats
API to fetch the total number of products, included in the store, and excluded from the store and other stats. It is categorised as a Read tool in the GoHighLevel MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GoHighLevel MCP Server MCP server in PolicyLayer and add a rule for get-product-store-stats: 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.
get-product-store-stats 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 get-product-store-stats 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 get-product-store-stats. 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.
get-product-store-stats 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.
More on GoHighLevel MCP Server, and thousands of servers like it.
This server
Across the catalogue