AI agents use create_collection to create or update resources in Zotero — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Zotero environment.
This tool creates a new collection, which is a reversible write operation (collections can be deleted). It does not execute arbitrary code, delete data, move money, or read sensitive information in isolation. The blast radius is low since creating unwanted collections in a reference library is easily recoverable.
From the tool's definition Tool name 'create_collection' and description 'Create a new collection in the Zotero library' indicate irreversible creation of a new data structure within a reference management system.
Attacks that exploit this kind of access
Create a new collection in the Zotero library. It is categorised as a Write tool in the Zotero MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Zotero MCP server in PolicyLayer and add a rule for create_collection: 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.
create_collection is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_collection 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 create_collection. 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.
create_collection is provided by the Zotero MCP server (cr625/zotero-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
create_collection is one line of Zotero's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →