restore_item
Restore one or more deleted (archived) items back to the Grabblist. Pass a single id or an array of ids for batch restore.
This record as markdown: /tools/com-grabbitapp-grabblist/restore-item.md
What restore_item does on Grabblist
AI agents use restore_item 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 | object | Yes | Item ID or array of item IDs to restore |
reason | string | — | Why this change was made (shown to user in change history) |
Parameters from the server's own tool schema.
Why restore_item is rated Medium
An AI agent can call restore_item 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 restore_item 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 restore_item, this is the rule to start with:
restore_item 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 restore_item call is checked against it from then on.
Questions about restore_item
Restore one or more deleted (archived) items back to the Grabblist. Pass a single id or an array of ids for batch restore. 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.
restore_item accepts 2 parameters: id, reason. 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 restore_item: 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.
restore_item 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 restore_item 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 restore_item. 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.
restore_item 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