upsert_zotero_mcp_endpoint · Scifinder Route MCP

WHAT IT DOES

What upsert_zotero_mcp_endpoint does on Scifinder Route

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

WHY IT NEEDS A POLICY

Why upsert_zotero_mcp_endpoint needs a policy

This tool modifies configuration state (a YAML file) by creating or updating an endpoint definition. It is reversible since configuration can be updated again or deleted. While it affects system configuration, it does not delete data (ruling out Destructive), execute arbitrary code (Execute), or handle financial operations.

From the tool's definition 'Create or update a Zotero MCP endpoint in the separate Web UI config YAML' — the verb 'create or update' directly indicates Write-class operations that modify configuration data reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

upsert_zotero_mcp_endpoint Rate-limited

upsert_zotero_mcp_endpoint 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": {
    "upsert_zotero_mcp_endpoint": {
      "limits": [
        {
          "counter": "upsert_zotero_mcp_endpoint_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 Scifinder Route, so you can run agents against it safely.

FAQ

Questions about upsert_zotero_mcp_endpoint

What does the upsert_zotero_mcp_endpoint tool do? +

Create or update a Zotero MCP endpoint in the separate Web UI config YAML. It is categorised as a Write tool in the Scifinder Route MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on upsert_zotero_mcp_endpoint? +

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

What risk level is upsert_zotero_mcp_endpoint? +

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

Can I rate-limit upsert_zotero_mcp_endpoint? +

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

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

upsert_zotero_mcp_endpoint is provided by the Scifinder Route MCP server (kettly1260/scifinder-route-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.