Add items to your Zotero library by resolving DOIs. Works with ANY item type that has a DOI — journal articles, books, datasets, preprints, conference papers, reports, etc. For each DOI, resolves metadata via content negotiation and creates the item in Zotero with the correct type automatically. ...
AI agents use add_items_by_doi to create or update resources in Mcp Zotero — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Zotero environment.
This tool creates new records in the user's Zotero library by resolving DOIs and adding items. While this modifies data, it is reversible (items can be deleted via delete_items tool on the same server), so it is categorized as Write rather than Destructive.
From the tool's definition The tool description explicitly states 'Add items to your Zotero library' and 'creates the item in Zotero', which are create/write operations. It also mentions 'attaches OA PDFs', indicating modification of the library state.
Documented attack patterns abuse exactly the kind of access add_items_by_doi gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Zotero, and nothing reaches the server without passing your rules. This is the rule we recommend for add_items_by_doi:
{
"version": "1",
"default": "deny",
"tools": {
"add_items_by_doi": {
"limits": [
{
"counter": "add_items_by_doi_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_items_by_doi 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.
Add items to your Zotero library by resolving DOIs. Works with ANY item type that has a DOI — journal articles, books, datasets, preprints, conference papers, reports, etc. For each DOI, resolves metadata via content negotiation and creates the item in Zotero with the correct type automatically. Returns a list of successfully added items (with item_key and title) and any failures. WHEN TO USE vs add_items: - Use add_items_by_doi when the item HAS a DOI — it auto-resolves all metadata and attaches OA PDFs. - Use add_items when the item does NOT have a DOI, or when you need to override specific metadata fields (add_items_by_doi does not allow metadata overrides). - Mixed batch: if some items have DOIs and others don. It is categorised as a Write tool in the Mcp Zotero MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Zotero MCP server in PolicyLayer and add a rule for add_items_by_doi: 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 Mcp Zotero. Nothing to install.
add_items_by_doi 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 add_items_by_doi 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 add_items_by_doi. 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.
add_items_by_doi is provided by the Mcp Zotero MCP server (xevos117/mcp-zotero). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp 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.
13 Mcp Zotero tools catalogued and risk-classified — across an index of 43,000+ MCP servers.