Delete an item from the Zotero library.
AI agents call delete_item 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 permanently removes items from a user's Zotero library without possibility of undo. Deletion is an irreversible operation that destroys data. An AI agent with unconstrained access could maliciously or erroneously delete significant portions of a researcher's bibliography, causing data loss. This is the most severe category applicable.
From the tool's definition Tool name 'delete_item' and description 'Delete an item from the Zotero library.' explicitly indicate irreversible deletion of data.
Attacks that exploit this kind of access
Delete an item from the Zotero library. 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_item: 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_item 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_item 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_item. 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_item is provided by the Zotero MCP server (cr625/zotero-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
delete_item is one line of Zotero'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 →