This record as markdown: /tools/ghl/ghl-list-products.md
What ghl_list_products does on Ghl
AI agents call ghl_list_products 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 |
|---|---|---|---|
limit | number | — | Maximum number of products to return |
offset | number | — | Number of products to skip |
search | string | — | Search term for product names |
storeId | string | — | Filter by store ID |
locationId | string | — | GHL Location ID (optional, uses default if not provided) |
includedInStore | boolean | — | Filter by store inclusion status |
availableInStore | boolean | — | Filter by store availability |
Parameters from the server's own tool schema.
Why ghl_list_products is rated Low
This tool queries and retrieves product data without creating, modifying, deleting, or executing any operations. It performs a read-only action consistent with 'list' and 'get' operations, making it a Read category risk. The optional filtering capability does not change its fundamental nature as a data retrieval operation.
From the tool's definition Tool name 'ghl_list_products' and description 'List products with optional filtering' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs ghl_list_products 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_list_products, this is the rule to start with:
ghl_list_products 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_list_products call is checked against it from then on.
Questions about ghl_list_products
List products with optional filtering. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
ghl_list_products accepts 7 parameters: limit, offset, search, storeId, locationId, includedInStore, availableInStore. 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_list_products: 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_list_products 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_list_products 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_list_products. 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_list_products 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