zotero_update_collection

A write tool on the Zotero MCP server.

SERVERZotero MCP SOURCEpypi:zotero-mcp-server

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/54yyyu-zotero-mcp/zotero-update-collection.md

WHAT IT DOES

What zotero_update_collection does on Zotero MCP

AI agents use zotero_update_collection to create or update resources in Zotero MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Zotero MCP environment.

RISK

Why zotero_update_collection is rated Medium

Modifies collection structure or metadata, reversible but affects research library organization.

From the tool's definition uninformative description; 'update_collection' suggests modifying collection metadata or organization.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs zotero_update_collection safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Zotero MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For zotero_update_collection, this is the rule to start with:

zotero_update_collection Rate-limited

zotero_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": {
    "zotero_update_collection": {
      "limits": [
        {
          "counter": "zotero_update_collection_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Zotero MCP, apply this rule, and every zotero_update_collection call is checked against it from then on.

FAQ

Questions about zotero_update_collection

What does the zotero_update_collection tool do? +

zotero_update_collection is a write tool on the Zotero MCP server. It is categorised as a Write tool in the Zotero MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on zotero_update_collection? +

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

What risk level is zotero_update_collection? +

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

Can I rate-limit zotero_update_collection? +

Yes. Add a rate_limit block to the zotero_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 zotero_update_collection completely? +

Set action: deny in the PolicyLayer policy for zotero_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 zotero_update_collection? +

zotero_update_collection is provided by the Zotero MCP server (pypi:zotero-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Zotero, and thousands of servers like it.

This server

All 55 Zotero tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →