register_document · Scifinder Route MCP: Risk & Policy

WHAT IT DOES

What register_document does on Scifinder Route

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

This tool adds new structured data (a parsed SciFinder export) to the local indexed database. While it does not delete or destroy data (ruling out Destructive), does not execute arbitrary code or trigger external operations (ruling out Execute), and does not move money (ruling out Financial), it clearly modifies the system state by registering and indexing new documents. This fits Write semantics.

From the tool's definition Tool description states 'Register and parse a local SciFinder export file' — this creates or records a new document entry in the indexed database. The verb 'register' indicates persistent data creation or modification of the search index.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

register_document Rate-limited

register_document 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": {
    "register_document": {
      "limits": [
        {
          "counter": "register_document_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 register_document

What does the register_document tool do? +

Register and parse a local SciFinder export file already visible to the server. 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 register_document? +

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

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

Can I rate-limit register_document? +

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

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

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