zotero_delete_collection
A destructive tool on the Zotero MCP server.
This record as markdown: /tools/54yyyu-zotero-mcp/zotero-delete-collection.md
What zotero_delete_collection does on Zotero MCP
AI agents call zotero_delete_collection to permanently remove resources in Zotero MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why zotero_delete_collection is rated Critical
The tool name contains 'delete', which performs irreversible removal of a Zotero collection and its associated data. This is a destructive operation that cannot be easily undone and results in loss of research library organization and potentially metadata. Although the description is empty, the clear naming convention makes the intent unambiguous.
From the tool's definition Tool name is 'zotero_delete_collection' which directly indicates deletion of a collection. The verb 'delete' is associated with irreversible removal of data.
Attacks that exploit this kind of access
The rule that runs zotero_delete_collection safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Zotero MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For zotero_delete_collection, this is the rule to start with:
zotero_delete_collection is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Zotero MCP, apply this rule, and every zotero_delete_collection call is checked against it from then on.
Questions about zotero_delete_collection
zotero_delete_collection is a destructive tool on the Zotero MCP server. It is categorised as a Destructive tool in the Zotero MCP 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 zotero_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 MCP. Nothing to install.
zotero_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 zotero_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 zotero_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.
zotero_delete_collection is provided by the Zotero MCP server (pypi:zotero-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Zotero, and thousands of servers like it.
Across the catalogue