// MCP TOOL REFERENCE

delete_collection

ServerZotero
CategoryDestructive

WHAT IT DOES

What delete_collection does on Zotero

AI agents call delete_collection to permanently remove resources in Zotero — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

THE RISK

Critical Risk

Why delete_collection needs a policy

This tool irreversibly deletes collections and optionally trashes associated items, which cannot be undone. Even the default behavior (removing items from collection) is destructive to the collection structure. The optional deleteItems parameter elevates this to a data-loss risk. Destructive operations have higher severity than Write or Execute operations due to their irreversible nature.

From the tool's definition Tool name is 'delete_collection' and description states 'WARNING: This is a destructive operation' and explicitly mentions the ability to send items to trash with deleteItems=true parameter.

Documented attack patterns abuse exactly the kind of access delete_collection gives an agent:

POLICY

How to control delete_collection

PolicyLayer is an MCP gateway — it sits between your AI agents and Zotero, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_collection:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_collection"
  ]
}

delete_collection disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Zotero — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Zotero tools

Write remove_items_from_collection Remove one or more items from a collection. Items are NOT deleted from the library, only r Write add_items_to_collection Add one or more items to a collection by their item keys. Write create_collection Create a new collection in the library. Optionally nest it under a parent collection. Write update_collection Rename or move an existing collection. Provide name to rename, parentCollection to move (e Write write_item Create a new Zotero item, re-parent existing attachments, or import a local file as an att Write write_metadata Update metadata fields on Zotero items (title, abstract, date, URL, DOI, creators, etc.). Write write_note Create or modify Zotero notes. Supports child notes (attached to items), standalone notes, Write write_tag Add, remove, or replace tags on Zotero items. Works on any item type. Response includes be

All 27 Zotero tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Zotero → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about delete_collection

What does the delete_collection tool do? +

Delete a collection. WARNING: This is a destructive operation. By default, items in the collection are NOT deleted (only removed from the collection). Set deleteItems=true to also send items to trash. It is categorised as a Destructive tool in the Zotero MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_collection? +

Register the Zotero MCP server in PolicyLayer and add a rule for delete_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 Zotero. Nothing to install.

What risk level is delete_collection? +

delete_collection is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_collection? +

Yes. Add a rate_limit block to the delete_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.

How do I block delete_collection completely? +

Set action: deny in the PolicyLayer policy for delete_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.

What MCP server provides delete_collection? +

delete_collection is provided by the Zotero MCP server (zotero-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Zotero tool call.

Start from Zotero, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

27 Zotero tools catalogued and risk-classified — across an index of 43,000+ MCP servers.