This record as markdown: /tools/aiwerk-mcp-server-ghl/products-get-product-collection.md
What products_get_product_collection does on Ghl
AI agents call products_get_product_collection 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 |
|---|---|---|---|
name | string | — | Query to search collection based on names |
altId | string | — | Location Id Defaults to GHL_LOCATION_ID when omitted. |
limit | number | — | The maximum number of items to be included in a single page of results |
offset | number | — | The starting index of the page, indicating the position from which the results should be retrieved. |
altType | string | — | The type of alt. For now it is only LOCATION Defaults to GHL_LOCATION_ID when omitted. |
collectionIds | string | — | Ids of the collections separated by comma(,) for search purposes |
Parameters from the server's own tool schema.
Why products_get_product_collection is rated Low
Even though products_get_product_collection only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs products_get_product_collection 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 products_get_product_collection, this is the rule to start with:
products_get_product_collection 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 products_get_product_collection call is checked against it from then on.
Questions about products_get_product_collection
Fetch Product Collections. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
products_get_product_collection accepts 6 parameters: name, altId, limit, offset, altType, collectionIds. 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 products_get_product_collection: 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.
products_get_product_collection 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 products_get_product_collection 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 products_get_product_collection. 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.
products_get_product_collection is provided by the Ghl MCP server (@aiwerk/mcp-server-ghl). 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