Add, remove, or replace tags on Zotero items. Works on any item type. Response includes before/after tag lists for verification. Confirm with user before executing.
AI agents use write_tag 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.
The tool creates, modifies, and removes tags—metadata attributes on items. These are reversible Write operations: tags can be added, removed, or changed without permanent data loss. While tagging affects searchability and organization, it does not delete items, execute code, or trigger financial transactions.
From the tool's definition Tool description states 'Add, remove, or replace tags on Zotero items,' which are reversible modifications to item metadata. The note to 'Confirm with user before executing' acknowledges its Write nature.
Attacks that exploit this kind of access
Add, remove, or replace tags on Zotero items. Works on any item type. Response includes before/after tag lists for verification. 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_tag: 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_tag 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_tag 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_tag. 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_tag 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_tag 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 →