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 new collections (organizational folders) in Zotero, which is a reversible write operation. It modifies the library structure by adding a new container but does not execute code, delete data irreversibly, or move money. The impact is limited to creating a reference organization structure, making it a low-severity write action.
From the tool's definition Tool name is 'create_collection' and description states 'Create a new collection (folder) in the Zotero library.' The verb 'create' directly indicates data modification.
Attacks that exploit this kind of access
Create a new collection (folder) in the Zotero library. Collections help organize items into hierarchical folders. Use parentCollection to create a sub-collection. 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 (xbghc/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 →