add_item_by_doi · Zotero MCP: Risk & Policy

WHAT IT DOES

What add_item_by_doi does on Zotero

AI agents use add_item_by_doi 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.

WHY IT NEEDS A POLICY

Why add_item_by_doi needs a policy

This tool creates new items in the Zotero library by fetching metadata and adding entries. This is a Write operation: it modifies state by adding records to the library, but the changes are reversible (items can be deleted). The duplicate-checking safeguard and reliance on external metadata sources (CrossRef) further reduce severity. There is no data deletion, financial impact, or code execution involved.

From the tool's definition Tool description states it will "Add an item to the Zotero library" and "creates the item only if it does not already exist", indicating reversible creation of data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_item_by_doi Rate-limited

add_item_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_item_by_doi": {
      "limits": [
        {
          "counter": "add_item_by_doi_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Zotero, so you can run agents against it safely.

FAQ

Questions about add_item_by_doi

What does the add_item_by_doi tool do? +

Add an item to the Zotero library by DOI. Fetches metadata from CrossRef, checks for duplicates by DOI, and creates the item only if it does not already exist. 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.

How do I enforce a policy on add_item_by_doi? +

Register the Zotero MCP server in PolicyLayer and add a rule for add_item_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 Zotero. Nothing to install.

What risk level is add_item_by_doi? +

add_item_by_doi is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit add_item_by_doi? +

Yes. Add a rate_limit block to the add_item_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.

How do I block add_item_by_doi completely? +

Set action: deny in the PolicyLayer policy for add_item_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.

What MCP server provides add_item_by_doi? +

add_item_by_doi is provided by the Zotero MCP server (masaki39/zotero-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.