zotero_batch_update_tags · Zotero MCP Server MCP

WHAT IT DOES

What zotero_batch_update_tags does on Zotero MCP Server

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

WHY IT NEEDS A POLICY

Why zotero_batch_update_tags needs a policy

This tool modifies tags on potentially multiple items in a Zotero library. Tags are metadata that can be changed but the operation is reversible (tags can be re-edited or restored). While it affects multiple items via a search query (broader blast radius than single-item updates), it does not delete data or trigger external financial/code execution effects. It falls squarely in the Write category.

From the tool's definition Tool name includes 'batch_update_tags' and description states 'Batch update tags across multiple items' - these are modification operations that change item metadata.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

zotero_batch_update_tags Rate-limited

zotero_batch_update_tags 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_batch_update_tags": {
      "limits": [
        {
          "counter": "zotero_batch_update_tags_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 Zotero MCP Server, so you can run agents against it safely.

FAQ

Questions about zotero_batch_update_tags

What does the zotero_batch_update_tags tool do? +

Batch update tags across multiple items matching a search query. It is categorised as a Write tool in the Zotero MCP Server 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_batch_update_tags? +

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

What risk level is zotero_batch_update_tags? +

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

Can I rate-limit zotero_batch_update_tags? +

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

Set action: deny in the PolicyLayer policy for zotero_batch_update_tags. 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_batch_update_tags? +

zotero_batch_update_tags is provided by the Zotero MCP Server MCP server (tspspi/zotero-mcp-postgres-ollama-fulltext). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.