// SCAN REPORT

Grabblist

23 tools. 15 can modify or destroy data without limits.

4 destructive tools with no built-in limits. Policy required.

Last updated: 20 Aug 2026

15 can modify or destroy data

8 read-only

23 tools total

Community server · catalogue entry checked 20/08/2026 · full schemas captured for 22 of 23 tools

How to control Grabblist ↓

TOOL MAP

What Grabblist exposes to your agents

Read (8) Write / Execute (11) Destructive / Financial (4)

Running more than one server? Check your whole stack →

CONTEXT-WINDOW COST

What Grabblist costs in tokens

4,118 tokens of tool definitions, loaded on every request

2.1% of a 200k context window

702 heaviest tool: add_item

Full per-tool breakdown → Model it in the token calculator →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Grabblist tools

Destructive · High delete_collection Permanently delete a collection. Items inside are not deleted — they stay in the Grabblist. Destructive · High delete_item Remove one or more items from the user's Grabblist (soft-delete). Pass a single id or an array of ids for batch operations. Destructive · High 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 st Destructive · High unlink_items Remove a relation between two items.

15 of Grabblist's 23 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Grabblist

PolicyLayer is an MCP gateway — it sits between your AI agents and Grabblist, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "delete_collection": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "add_item": {
    "limits": [
      {
        "counter": "add_item_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "ask_agent": {
    "limits": [
      {
        "counter": "ask_agent_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Grabblist — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON GRABBLIST →

Instant setup, no code required.

FULL CATALOGUE

All 23 Grabblist tools

DESTRUCTIVE 4 tools

Destructive delete_collection Permanently delete a collection. Items inside are not deleted — they stay in the Grabblist. Destructive delete_item Remove one or more items from the user's Grabblist (soft-delete). Pass a single id or an array of ids for batc Destructive 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. I Destructive unlink_items Remove a relation between two items.

WRITE 11 tools

Write add_item Save an item to the user's Grabblist. Creates a static snapshot — Grabblist does not monitor prices or auto-up Write add_to_collection Add a saved item to a collection. Both the item and collection must already exist. Write create_collection Create a new collection (folder) in the user's Grabblist to organize saved items. Write link_items Create typed relations between items: alternative (A or B), complement (A and B together), upgrade (B replaces Write ping Test connectivity to Grabblist and return service version. Write restore_item Restore one or more deleted (archived) items back to the Grabblist. Pass a single id or an array of ids for ba Write send_feedback Send feedback, bug report, or feature request to the Grabbit team. Use this when you encounter parsing failure Write set_pinned_items Set the pinned "Top Picks" items for a collection (max 3). Pinned items are highlighted on the share page. Write update_collection Update a collection's name, icon, description, budget, or sharing status. Only provide the fields you want to Write update_item Edit fields on one or more saved items. Pass a single id or an array of ids for batch updates (same fields app Write update_price Manually update the price on a saved item. Records old and new price for comparison. This is a manual correcti

READ 8 tools

Read ask_agent Delegate a task to Grabblist's built-in AI assistant. The agent knows the user's Grabblist and can answer ques Read get_collection_activity Get recent activity on a collection — additions, removals, edits. Read get_item Get full details of a saved item by ID. Returns a static snapshot from the user's Grabblist. Read get_item_graph Get all relations for an item — alternatives, complements, upgrades, duplicates. Returns the item and all conn Read get_item_history Get the change history for a saved item — who changed what and when. Read get_wishlist Get all saved items from the user's Grabblist. Each item is a static snapshot — data reflects the moment it wa Read list_collections List all collections OR get a specific collection with its items. Without id: returns all collections with cou Read search_saved Search within the user's saved items by keyword

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Grabblist

Can an AI agent delete data through the Grabblist MCP server? +

Yes. The Grabblist server exposes 4 destructive tools including delete_collection, delete_item, remove_from_collection. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Grabblist? +

The Grabblist server has 11 write tools including add_item, add_to_collection, create_collection. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Grabblist.

How many tools does the Grabblist MCP server expose? +

23 tools across 3 categories: Destructive, Read, Write. 8 are read-only. 15 can modify, create, or delete data.

How do I enforce a policy on Grabblist? +

Register the Grabblist MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Grabblist tool call.

Deterministic rules across all 23 Grabblist tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON GRABBLIST →

Instant setup, no code required.

23 Grabblist tools catalogued and risk-classified — across an index of 46,500+ MCP servers.

// WHERE THIS COMES FROM

These policies come from Grabblist's registry record.

The record behind this page: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →