New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

zotero_delete_annotation

A destructive tool on the Zotero MCP server.

SERVERZotero MCP SOURCEpypi:zotero-mcp-server
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/54yyyu-zotero-mcp/zotero-delete-annotation.md

What zotero_delete_annotation does on Zotero MCP

AI agents call zotero_delete_annotation 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_annotation is rated Critical

Deletion operations are irreversible and cannot be undone. Even though annotations are typically auxiliary metadata rather than primary research data, their loss is permanent and could disrupt research workflows, note-taking, or citation analysis.

From the tool's definition Tool name explicitly contains 'delete' combined with 'annotation', indicating irreversible removal of data. The verb 'delete' is a canonical destructive operation. Tool description is empty, which slightly reduces confidence, but the name alone is unambiguous.

Questions about zotero_delete_annotation

What does the zotero_delete_annotation tool do? +

zotero_delete_annotation 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.

How do I enforce a policy on zotero_delete_annotation? +

Register the Zotero MCP server in PolicyLayer and add a rule for zotero_delete_annotation: 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.

What risk level is zotero_delete_annotation? +

zotero_delete_annotation 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 zotero_delete_annotation? +

Yes. Add a rate_limit block to the zotero_delete_annotation 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 zotero_delete_annotation completely? +

Set action: deny in the PolicyLayer policy for zotero_delete_annotation. 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 zotero_delete_annotation? +

zotero_delete_annotation 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Zotero's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.