update_collection
Update a collection's name, icon, description, budget, or sharing status. Only provide the fields you want to change — omitted fields stay unchanged. Set is_public=true to share (returns public URL), is_public=false to unshare.
This record as markdown: /tools/com-grabbitapp-grabblist/update-collection.md
What update_collection does on Grabblist
AI agents use update_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 |
|---|---|---|---|
id | string | Yes | The collection ID to update |
icon | string | — | Material Symbols icon name (e.g. "devices", "home", "shopping_bag") |
name | string | — | New collection name |
color | string | — | Hex color (e.g. "#3B82F6", "#22C55E", "#EF4444") |
budget | number | — | New budget amount |
reason | string | — | Why this change was made (shown to user in change history) |
is_public | boolean | — | Set true to share (generates public URL), false to unshare |
description | string | — | New description |
budget_currency | string | — | New budget currency |
Parameters from the server's own tool schema.
Why update_collection is rated Medium
An AI agent can call update_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 update_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 update_collection, this is the rule to start with:
update_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 update_collection call is checked against it from then on.
Questions about update_collection
Update a collection's name, icon, description, budget, or sharing status. Only provide the fields you want to change — omitted fields stay unchanged. Set is_public=true to share (returns public URL), is_public=false to unshare. 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.
update_collection accepts 9 parameters: id, icon, name, color, budget, reason, is_public, description, budget_currency. Required: id. 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 update_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.
update_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 update_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 update_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.
update_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