update_collection · Mcp Zotero MCP: Risk & Policy

WHAT IT DOES

What update_collection does on Mcp Zotero

AI agents use update_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.

WHY IT NEEDS A POLICY

Why update_collection needs a policy

This tool creates or modifies data (a collection's properties) in a reversible manner. The changes can be undone by updating again to previous values. It does not delete, execute arbitrary code, move money, or retrieve data. Write is the correct category.

From the tool's definition Tool description states 'Update a collection's name or parent' — this modifies metadata of an existing collection reversibly. The verb 'update' combined with the ability to change name and parent relationship confirms write-class behavior.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_collection Rate-limited

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.

View as policy code

policy.json

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

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Mcp Zotero, so you can run agents against it safely.

FAQ

Questions about update_collection

What does the update_collection tool do? +

Update a collection's name or parent. 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.

How do I enforce a policy on update_collection? +

Register the Mcp 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 Mcp 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 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.