Clear the full-text processing queue.
AI agents call zotero_clear_fulltext_processing_queue to permanently remove resources in Zotero MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Clearing a processing queue discards all pending work items that have not yet been processed. This action is irreversible — once the queue is cleared, those queued items and their processing state are gone and cannot be recovered without re-queuing them manually. This qualifies as Destructive rather than Write since the operation permanently removes queued state rather than modifying it reversibly.
From the tool's definition 'Clear the full-text processing queue' — clearing a queue irreversibly removes pending processing jobs
Attacks that exploit this kind of access
Clear the full-text processing queue. It is categorised as a Destructive tool in the Zotero MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Zotero MCP Server MCP server in PolicyLayer and add a rule for zotero_clear_fulltext_processing_queue: 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 Server. Nothing to install.
zotero_clear_fulltext_processing_queue 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_clear_fulltext_processing_queue 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_clear_fulltext_processing_queue. 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_clear_fulltext_processing_queue is provided by the Zotero MCP Server MCP server (tspspi/zotero-mcp-postgres-ollama-fulltext). 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 →