remove_from_collection
Remove one or more items from a collection. Pass a single item_id or an array of item_ids for batch removal. Items are NOT deleted — they stay in the Grabblist.
This record as markdown: /tools/com-grabbitapp-grabblist/remove-from-collection.md
What remove_from_collection does on Grabblist
AI agents call remove_from_collection to permanently remove resources in Grabblist, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
reason | string | — | Why this change was made (shown to user in change history) |
item_ids | object | Yes | Item ID or array of item IDs to remove |
collection_id | string | Yes | The collection ID |
Parameters from the server's own tool schema.
Why remove_from_collection is rated Critical
An AI agent that decides to call remove_from_collection doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Grabblist is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs remove_from_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 remove_from_collection, this is the rule to start with:
remove_from_collection is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Grabblist, apply this rule, and every remove_from_collection call is checked against it from then on.
Questions about remove_from_collection
Remove one or more items from a collection. Pass a single item_id or an array of item_ids for batch removal. Items are NOT deleted — they stay in the Grabblist. It is categorised as a Destructive tool in the Grabblist MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
remove_from_collection accepts 3 parameters: reason, item_ids, collection_id. Required: item_ids, collection_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 remove_from_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.
remove_from_collection is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_from_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 remove_from_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.
remove_from_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.
Across the catalogue