Build or update the semantic search index from Zotero library or collection.
AI agents invoke index_library to trigger actions in Mcp Zotero. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
index_library executes an indexing process rather than simply reading or writing data. It triggers semantic search index generation from PDFs via local embeddings, which is a computational operation that modifies system state (the index itself). While not destructive or financial, it clearly executes external processes.
From the tool's definition Tool performs 'build or update' operations on a semantic search index, which involves running computational processes (embedding generation, index construction) whose effects depend on which library/collection is indexed.
Attacks that exploit this kind of access
Build or update the semantic search index from Zotero library or collection. It is categorised as a Execute tool in the Mcp Zotero MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Zotero MCP server in PolicyLayer and add a rule for index_library: 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.
index_library is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the index_library 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 index_library. 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.
index_library 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 →