update_collection

THE RISK

Medium Risk

Why update_collection needs a policy

This tool creates or modifies data (collection name and hierarchy) without permanently removing anything. Renaming and moving are reversible operations, making it a Write rather than Destructive action. The scope is limited to collection organization within a reference management system, so severity is medium rather than high.

From the tool's definition Tool description states 'Rename or move an existing collection' — these are reversible modifications to collection metadata. The parameters (name, parentCollection) confirm structural updates rather than deletion or data destruction.

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

POLICY

How to control update_collection

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

policy.json

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

update_collection 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 write_item Create a new Zotero item, re-parent existing attachments, or import a local file as an att Write write_metadata Update metadata fields on Zotero items (title, abstract, date, URL, DOI, creators, etc.). 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 update_collection

What does the update_collection tool do? +

Rename or move an existing collection. Provide name to rename, parentCollection to move (empty string moves to top level). 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 update_collection? +

Register the Zotero MCP server in PolicyLayer and add a rule for update_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 Zotero. Nothing to install.

What risk level is update_collection? +

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

Can I rate-limit update_collection? +

Yes. Add a rate_limit block to the update_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.

How do I block update_collection completely? +

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

What MCP server provides update_collection? +

update_collection 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 →