AI agents call list_items to retrieve information from Zotero without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool lists items from a Zotero library—a pure read operation with no side effects, data modification, or external execution. The read-only server context and naming pattern confirm it belongs in the Read category. Severity is low because the blast radius of accidental misuse is limited to unwanted information retrieval from a reference library.
From the tool's definition Server described as 'Read-only MCP server for browsing, searching, and exporting a Zotero library.' Tool name 'list_items' combined with context of sibling tools (list_collections, list_saved_searches, get_item, get_note) indicates this is a query/listing…
Attacks that exploit this kind of access
list_items. It is categorised as a Read tool in the Zotero MCP Server, which means it retrieves data without modifying state.
Register the Zotero MCP server in PolicyLayer and add a rule for list_items: 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.
list_items is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_items 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 list_items. 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.
list_items is provided by the Zotero MCP server (nadavweisler/zotero-mcp). 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 →