Create a new Zotero item, re-parent existing attachments, or import a local file as an attachment. Common workflows: (1) read PDF → extract metadata → create item → attach PDF via attachmentKeys; (2) convert PDF to Markdown → import the .md file as attachment via import action. Confirm with user ...
AI agents use write_item to create or update resources in Zotero Agent — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Zotero Agent environment.
This tool creates new research library entries and modifies attachment relationships—both reversible write operations. While it modifies the Zotero knowledge base, changes can be undone by deleting items or re-organizing attachments, distinguishing it from destructive operations.
From the tool's definition Tool description explicitly states it can 'Create a new Zotero item' and 'import a local file as an attachment', which are write operations that create or modify data reversibly.
Attacks that exploit this kind of access
Create a new Zotero item, re-parent existing attachments, or import a local file as an attachment. Common workflows: (1) read PDF → extract metadata → create item → attach PDF via attachmentKeys; (2) convert PDF to Markdown → import the .md file as attachment via import action. Confirm with user before executing. It is categorised as a Write tool in the Zotero Agent MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Zotero Agent MCP server in PolicyLayer and add a rule for write_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 Agent. Nothing to install.
write_item 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 write_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.
Set action: deny in the PolicyLayer policy for write_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.
write_item is provided by the Zotero Agent MCP server (psiQAQ/zotero-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
write_item is one line of Zotero Agent's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →