record_doi_verification · Scifinder Route MCP: Risk & Policy

WHAT IT DOES

What record_doi_verification does on Scifinder Route

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

The tool writes/creates a verification record in the database. 'Record' indicates a write operation that stores verification results. It creates new data (a verification record) reversibly without deleting or executing code. Severity is medium as misuse could corrupt verification integrity for synthesis route literature links.

From the tool's definition Record DOI source verification performed by an agent or browser workflow

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

record_doi_verification Rate-limited

record_doi_verification 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": {
    "record_doi_verification": {
      "limits": [
        {
          "counter": "record_doi_verification_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 record_doi_verification

What does the record_doi_verification tool do? +

Record DOI source verification performed by an agent or browser workflow. 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 record_doi_verification? +

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

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

Can I rate-limit record_doi_verification? +

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

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

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