push_to_zotero · BioCite- MCP: Risk & Policy

WHAT IT DOES

What push_to_zotero does on BioCite-MCP

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

WHY IT NEEDS A POLICY

Why push_to_zotero needs a policy

This tool performs a write operation by pushing bibliographic data to Zotero, which creates or modifies reference entries. While reversible (entries can be deleted from Zotero), it commits data to an external system and could clutter or alter a user's bibliography if misused. Not destructive (data remains recoverable), not financial, and not execute-level (no arbitrary code execution).

From the tool's definition Tool name 'push_to_zotero' indicates writing/exporting data to an external reference management system (Zotero).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

push_to_zotero Rate-limited

push_to_zotero 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": {
    "push_to_zotero": {
      "limits": [
        {
          "counter": "push_to_zotero_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 BioCite-MCP, so you can run agents against it safely.

FAQ

Questions about push_to_zotero

What does the push_to_zotero tool do? +

push_to_zotero. It is categorised as a Write tool in the BioCite-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 push_to_zotero? +

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

What risk level is push_to_zotero? +

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

Can I rate-limit push_to_zotero? +

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

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

push_to_zotero is provided by the BioCite- MCP server (muslus/biocite-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.