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.
AI agents call delete_collection to permanently remove resources in Zotero Agent — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes collections and optionally irreversibly deletes items by sending them to trash. The operation cannot be undone, fitting the Destructive category. While the default behavior (removing items from collection only) is reversible, the enabled capability to delete items makes this a destructive tool.
From the tool's definition Tool name is 'delete_collection' and description explicitly states 'This is a destructive operation' and mentions capability to send items to trash with deleteItems=true parameter.
Attacks that exploit this kind of access
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 Agent MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Zotero Agent 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 Agent. 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 Agent MCP server (psiQAQ/zotero-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
delete_collection is one line of Zotero Agent's registry record.
The record carries the whole server: 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 →