remove_items_from_collection · Zotero Agent MCP

WHAT IT DOES

What remove_items_from_collection does on Zotero Agent

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

WHY IT NEEDS A POLICY

Why remove_items_from_collection needs a policy

The tool modifies collection membership by removing items, but explicitly states items are not deleted from the library. This is a reversible write operation (items can be re-added to the collection), not a destructive one. The blast radius is medium since misuse could disorganize a research library but no data is permanently lost.

From the tool's definition Remove one or more items from a collection. Items are NOT deleted from the library, only removed from this collection.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

remove_items_from_collection Rate-limited

remove_items_from_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": {
    "remove_items_from_collection": {
      "limits": [
        {
          "counter": "remove_items_from_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 Zotero Agent, so you can run agents against it safely.

FAQ

Questions about remove_items_from_collection

What does the remove_items_from_collection tool do? +

Remove one or more items from a collection. Items are NOT deleted from the library, only removed from this collection. It is categorised as a Write tool in the Zotero Agent MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on remove_items_from_collection? +

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

What risk level is remove_items_from_collection? +

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

Can I rate-limit remove_items_from_collection? +

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

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

remove_items_from_collection is provided by the Zotero Agent MCP server (psiQAQ/zotero-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

remove_items_from_collection is one line of Zotero Agent's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →