Create a new collection in the library. Optionally nest it under a parent collection.
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 in Zotero's library system. Collection creation is a Write operation: it adds new organizational metadata to the library but is fully reversible (collections can be deleted via delete_collection). There is no data deletion, financial impact, or arbitrary code execution.
From the tool's definition Tool description states 'Create a new collection in the library' - the word 'Create' indicates data creation/addition with reversible effects. Zotero collections are organizational containers that can be modified, renamed, or deleted later.
Documented attack patterns abuse exactly the kind of access create_collection gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Zotero, and nothing reaches the server without passing your rules. This is the rule we recommend for create_collection:
{
"version": "1",
"default": "deny",
"tools": {
"create_collection": {
"limits": [
{
"counter": "create_collection_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} create_collection stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a new collection in the library. Optionally nest it under a parent 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 (zotero-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Zotero, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
27 Zotero tools catalogued and risk-classified — across an index of 43,000+ MCP servers.