Add an item to a collection.
AI agents use add_item_to_collection to create or update resources in Mcp Zotero — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Zotero environment.
This tool creates or modifies collection membership by adding items, which is a reversible Write operation. The severity is medium because misuse could clutter or reorganize a user's library structure, but the action is reversible (items can be removed from collections). It affects data organization but not preservation or deletion.
From the tool's definition Tool name 'add_item_to_collection' and description 'Add an item to a collection' indicate a create/modify operation that changes collection membership.
Attacks that exploit this kind of access
Add an item to a collection. It is categorised as a Write tool in the Mcp Zotero MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Zotero MCP server in PolicyLayer and add a rule for add_item_to_collection: 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 Mcp Zotero. Nothing to install.
add_item_to_collection 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_item_to_collection 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_item_to_collection. 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_item_to_collection is provided by the Mcp Zotero MCP server (nealcaren/mcp-zotero). 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 →