get_collections
Get collections in the library. By default returns a flat, paginated list of top-level collections. Use recursive=true to retrieve the complete nested collection tree (all levels) in one call. Use parentCollection to scope to a specific parent\
This record as markdown: /tools/zotero/get-collections.md
What get_collections does on Zotero
AI agents call get_collections to retrieve information from Zotero without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_collections is rated Low
This tool retrieves collection metadata from a Zotero library without any side effects. It supports pagination and recursive retrieval of hierarchical data, but performs no write, delete, execute, or financial operations. The blast radius of misuse is minimal—an AI agent could retrieve all collections, but cannot modify, delete, or execute actions. This is a straightforward Read category tool with low severity.
From the tool's definition Tool name is 'get_collections' and description states it 'Get collections in the library' with options to retrieve nested structures.
Attacks that exploit this kind of access
The rule that runs get_collections safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Zotero, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_collections, this is the rule to start with:
get_collections is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Zotero, apply this rule, and every get_collections call is checked against it from then on.
Questions about get_collections
Get collections in the library. By default returns a flat, paginated list of top-level collections. Use recursive=true to retrieve the complete nested collection tree (all levels) in one call. Use parentCollection to scope to a specific parent\. 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 get_collections: 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.
get_collections 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 get_collections 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 get_collections. 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.
get_collections is provided by the Zotero MCP server (zotero-mcp). 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.
This server
Across the catalogue