reject_literature_link · Scifinder Route MCP: Risk & Policy

WHAT IT DOES

What reject_literature_link does on Scifinder Route

AI agents use reject_literature_link 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 reject_literature_link needs a policy

This is a Write operation because it modifies metadata about a literature link (changing its acceptance/rejection status), reversible through counter-operations like 'confirm_literature_link'. It is not Destructive because rejection does not permanently erase data — the link record and metadata persist, only its validation status changes.

From the tool's definition Tool description states it will "Reject an incorrect candidate Zotero literature link" — this modifies the state of a literature link record by changing its status/acceptance state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

reject_literature_link Rate-limited

reject_literature_link 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": {
    "reject_literature_link": {
      "limits": [
        {
          "counter": "reject_literature_link_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 reject_literature_link

What does the reject_literature_link tool do? +

Reject an incorrect candidate Zotero literature link. 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 reject_literature_link? +

Register the Scifinder Route MCP server in PolicyLayer and add a rule for reject_literature_link: 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 reject_literature_link? +

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

Can I rate-limit reject_literature_link? +

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

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

reject_literature_link 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.