AI agents use add_tags_to_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.
This tool modifies item metadata (tags) reversibly. It does not execute arbitrary code, delete data irreversibly, move money, or trigger external operations with unpredictable side effects. The worst-case misuse is adding unwanted tags to items, which is easily corrected by removing them. This is clearly Write category with low severity due to the reversible and isolated nature of the operation.
From the tool's definition Tool name 'add_tags_to_item' and description 'Add one or more tags to an existing item' indicate creation/modification of metadata on an existing resource. Tags are reversible metadata—they can be modified, updated, or removed without data loss.
Attacks that exploit this kind of access
Add one or more tags to an existing item. Tags are useful for organizing and filtering items. Duplicate tags are automatically ignored. 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.
Register the Zotero MCP server in PolicyLayer and add a rule for add_tags_to_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.
add_tags_to_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 add_tags_to_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 add_tags_to_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.
add_tags_to_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →