update_item · Zotero Assistant MCP: Risk & Policy

WHAT IT DOES

What update_item does on Zotero Assistant

AI agents use update_item to create or update resources in Zotero Assistant — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Zotero Assistant environment.

WHY IT NEEDS A POLICY

Why update_item needs a policy

This tool creates or modifies data in a reversible manner (the hallmark of Write category). It updates metadata on library items in Zotero, which is a side effect but not irreversible; changes can be undone or corrected. The severity is medium because misuse could corrupt or alter research metadata, potentially affecting scholarly work, but the damage is not necessarily catastrophic and can be remedied.

From the tool's definition Tool name is 'update_item' and description states 'Update metadata on an existing item' — this modifies existing data reversibly. The phrase 'Pass only fields to change' confirms it is a selective update operation, not a deletion or destructive action.

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 Assistant, so you can run agents against it safely.

FAQ

Questions about update_item

What does the update_item tool do? +

Update metadata on an existing item. Pass only fields to change. It is categorised as a Write tool in the Zotero Assistant 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 Assistant 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 Assistant. 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 Assistant MCP server (upascal/zotero-assistant-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.