write_metadata

Update metadata fields on Zotero items (title, abstract, date, URL, DOI, creators, etc.). Only works on regular items, not notes or attachments. Confirm with user before executing.

ServerZotero
CategoryWrite

How to control write_metadata ↓

WHAT IT DOES

What write_metadata does on Zotero

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

THE RISK

Medium Risk

Why write_metadata needs a policy

This tool creates or modifies data reversibly without deleting or destroying it. Users can undo or correct metadata changes. The emphasis on 'Confirm with user before executing' indicates awareness of potential misuse but doesn't elevate severity beyond Write. Medium severity reflects that widespread metadata corruption could affect research organization, but changes are not permanent or destructive.

From the tool's definition Tool description explicitly states 'Update metadata fields on Zotero items' — a direct modification operation. Covers reversible changes to item properties (title, abstract, date, URL, DOI, creators, etc.).

Documented attack patterns abuse exactly the kind of access write_metadata gives an agent:

POLICY

How to control write_metadata

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 write_metadata:

policy.json

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

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

Create a free account and register Zotero — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Zotero tools

Destructive delete_collection Delete a collection. WARNING: This is a destructive operation. By default, items in the co Write remove_items_from_collection Remove one or more items from a collection. Items are NOT deleted from the library, only r Write add_items_to_collection Add one or more items to a collection by their item keys. Write create_collection Create a new collection in the library. Optionally nest it under a parent collection. Write update_collection Rename or move an existing collection. Provide name to rename, parentCollection to move (e Write write_item Create a new Zotero item, re-parent existing attachments, or import a local file as an att Write write_note Create or modify Zotero notes. Supports child notes (attached to items), standalone notes, Write write_tag Add, remove, or replace tags on Zotero items. Works on any item type. Response includes be

All 27 Zotero tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about write_metadata

What does the write_metadata tool do? +

Update metadata fields on Zotero items (title, abstract, date, URL, DOI, creators, etc.). Only works on regular items, not notes or attachments. Confirm with user before executing. 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 write_metadata? +

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

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

Can I rate-limit write_metadata? +

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

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

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

Enforce policy on every Zotero tool call.

Start from Zotero, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

27 Zotero tools catalogued and risk-classified — across an index of 43,000+ MCP servers.