update_item · Zotero MCP: Risk & Policy

WHAT IT DOES

What update_item does on Zotero

AI agents use update_item 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 update_item needs a policy

The tool modifies existing Zotero reference metadata in a reversible manner. This is a Write operation because it creates or modifies data without permanent deletion. Severity is medium because unauthorized metadata updates could introduce inaccuracies into a user's research library, but the changes are not destructive or financial.

From the tool's definition Tool description explicitly states 'Update metadata fields of an existing item' and notes that 'other fields remain unchanged', indicating reversible modification of data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_item Rate-limited

update_item 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": {
    "update_item": {
      "limits": [
        {
          "counter": "update_item_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 update_item

What does the update_item tool do? +

Update metadata fields of an existing item. Only provide fields you want to change - other fields remain unchanged. Common fields: title, date, DOI, url, abstractNote, publicationTitle, volume, issue, pages, extra. 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 update_item? +

Register the Zotero MCP server in PolicyLayer and add a rule for update_item: 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 update_item? +

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

Can I rate-limit update_item? +

Yes. Add a rate_limit block to the update_item 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 update_item completely? +

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

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