// MCP TOOL REFERENCE

delete_collection

Delete a collection (folder) from your Zotero library. Items inside the collection are NOT deleted — they remain in your library. Requires UNSAFE_OPERATIONS environment variable set to

ServerMcp Zotero
CategoryDestructive

How to control delete_collection ↓

WHAT IT DOES

What delete_collection does on Mcp Zotero

AI agents call delete_collection to permanently remove resources in Mcp 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

Although items are not deleted, the collection itself is irreversibly removed, which destroys the organizational structure and metadata associations within the user's library. This is an irreversible operation that cannot be easily undone, fitting the Destructive category. The high severity reflects that an AI agent could remove important research organization without user awareness.

From the tool's definition Tool name is 'delete_collection' with description stating 'Delete a collection (folder) from your Zotero library.' The verb 'delete' and the irreversible nature of removing a collection structure qualifies this as destructive.

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 Mcp 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 Mcp 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 Mcp Zotero tools

Destructive delete_items Delete one or more items from your Zotero library permanently (moves to trash). Accepts up Write find_and_attach_pdfs For each Zotero item, check Unpaywall for open access PDFs and attach them. Items must hav Write add_items_by_doi Add items to your Zotero library by resolving DOIs. Works with ANY item type that has a DO Write add_linked_url_attachment Attach a linked URL to an existing Zotero item, or create a standalone linked-URL attachme Write create_collection Create a new collection (folder) in your Zotero library. Optionally nest it under a parent Write import_pdf_to_zotero Download a PDF from a URL and upload it to Zotero storage as an imported_url attachment. U Write inject_citations Replace <zcite> placeholder tags in a .docx file with native Zotero field codes that Zoter Read get_collection_items Get all items in a specific Zotero collection. Returns item keys, titles, authors, and dat

All 13 Mcp 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 Mcp 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 (folder) from your Zotero library. Items inside the collection are NOT deleted — they remain in your library. Requires UNSAFE_OPERATIONS environment variable set to. It is categorised as a Destructive tool in the Mcp 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 Mcp 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 Mcp 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 Mcp Zotero MCP server (xevos117/mcp-zotero). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Zotero tool call.

Start from Mcp 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.

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