create_collection
Create a new collection (folder) in the user's Grabblist to organize saved items.
This record as markdown: /tools/com-grabbitapp-grabblist/create-collection.md
What create_collection does on Grabblist
AI agents use create_collection to create or update resources in Grabblist, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Grabblist environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
icon | string | — | Material Symbols icon name (e.g. "devices", "home", "shopping_bag", "checkroom", "directions_car", "favorite"). Default: inventory_2 |
name | string | Yes | Collection name, e.g. "Gaming Setup" or "Gift Ideas" |
color | string | — | Hex color for the collection (e.g. "#3B82F6", "#22C55E", "#A855F7", "#EC4899", "#F59E0B", "#EF4444"). Default: #3B82F6 |
budget | number | — | Total spending target for this collection (e.g. 1500 for "Build PC under $1500") |
reason | string | — | Why this change was made (shown to user in change history) |
description | string | — | Short description of what this collection is for |
budget_currency | string | — | Currency for the budget (default: NZD) |
Parameters from the server's own tool schema.
Why create_collection is rated Medium
An AI agent can call create_collection faster than any human can review: one bad instruction and it creates or modifies resources in Grabblist by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs create_collection 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 create_collection, this is the rule to start with:
create_collection stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 create_collection call is checked against it from then on.
Questions about create_collection
Create a new collection (folder) in the user's Grabblist to organize saved items. It is categorised as a Write tool in the Grabblist MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_collection accepts 7 parameters: icon, name, color, budget, reason, description, budget_currency. Required: name. 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 create_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 Grabblist. Nothing to install.
create_collection is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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 create_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.
create_collection 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