Delete a collection from the library. Items in the collection are NOT deleted - they remain in the library. Sub-collections are also deleted.
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.
This tool irreversibly deletes data (collections and their hierarchical structure) from the Zotero library. Deletion cannot be undone programmatically, making it Destructive rather than Write. The blast radius is high because an agent could systematically delete a user's entire collection organization, though data loss is limited by the fact that items themselves are retained.
From the tool's definition Tool name is 'delete_collection' and description explicitly states 'Delete a collection from the library.' The action irreversibly removes a collection structure, and while items are preserved, sub-collections are also deleted without possibility of recovery.
Attacks that exploit this kind of access
Delete a collection from the library. Items in the collection are NOT deleted - they remain in the library. Sub-collections are also deleted. 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.
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.
delete_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 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.
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.
delete_collection is provided by the Zotero MCP server (xbghc/zotero-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →