list_collections
List all collections OR get a specific collection with its items. Without id: returns all collections with counts/values. With id: returns that collection's metadata and all items inside (with optional filters).
This record as markdown: /tools/com-grabbitapp-grabblist/list-collections.md
What list_collections does on Grabblist
AI agents call list_collections to retrieve information from Grabblist 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 |
|---|---|---|---|
id | string | — | Collection ID — if provided, returns that collection with all its items. If omitted, lists all collections. |
sort | string | — | Sort order (only when id is provided, default: newest) |
tags | array | — | Filter items that have ALL these tags (only when id is provided) |
status | string | — | Filter by decision status (only when id is provided) |
platform | string | — | Filter by platform domain name, e.g. "amazon", "ebay" (only when id is provided) |
max_price | number | — | Maximum price filter (only when id is provided) |
min_price | number | — | Minimum price filter (only when id is provided) |
created_by | string | — | Filter by who added: "ai" for AI-added items (only when id is provided) |
Parameters from the server's own tool schema.
Why list_collections is rated Low
Even though list_collections 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 list_collections safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Grabblist, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_collections, this is the rule to start with:
list_collections 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 Grabblist, apply this rule, and every list_collections call is checked against it from then on.
Questions about list_collections
List all collections OR get a specific collection with its items. Without id: returns all collections with counts/values. With id: returns that collection's metadata and all items inside (with optional filters). It is categorised as a Read tool in the Grabblist MCP Server, which means it retrieves data without modifying state.
list_collections accepts 8 parameters: id, sort, tags, status, platform, max_price, min_price, created_by. The full parameter table on this page comes from the server's own tool schema.
Register the Grabblist MCP server in PolicyLayer and add a rule for list_collections: 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 Grabblist. Nothing to install.
list_collections 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 list_collections 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 list_collections. 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.
list_collections is provided by the Grabblist MCP server (https://mcp.grabbitapp.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Grabblist, and thousands of servers like it.
This server
Across the catalogue