Remove items from the semantic search index.
AI agents call remove_from_index to permanently remove resources in Mcp Zotero — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool removes items from the semantic search index. Deletion from an index is typically irreversible without re-indexing, making this a Destructive operation. Severity is medium because only the search index entries are affected (not the underlying Zotero items themselves), but an AI agent misusing this could silently remove items from semantic search, degrading search functionality.
From the tool's definition 'Remove items from the semantic search index' — explicitly removes/deletes data from the index, which is an irreversible deletion operation
Attacks that exploit this kind of access
Remove items from the semantic search index. It is categorised as a Destructive tool in the Mcp Zotero MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Zotero MCP server in PolicyLayer and add a rule for remove_from_index: 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 Mcp Zotero. Nothing to install.
remove_from_index 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 remove_from_index 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 remove_from_index. 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.
remove_from_index is provided by the Mcp Zotero MCP server (nealcaren/mcp-zotero). 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 →