upload_document · Scifinder Route MCP: Risk & Policy

WHAT IT DOES

What upload_document does on Scifinder Route

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

This tool creates new document records and modifies the upload area by registering and parsing files. While it does not delete data (ruling out Destructive) and does not execute arbitrary code beyond parsing (ruling out Execute), it does create and modify persistent state in the system. The modification is reversible (files can be removed, records deleted), so it falls under Write rather than Execute.

From the tool's definition Tool description states 'Copy a server-visible file into the upload area, then register and parse it.' The verbs 'copy', 'register', and 'parse' indicate creation/modification of data in the upload area and registration of new documents in the system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

upload_document Rate-limited

upload_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": {
    "upload_document": {
      "limits": [
        {
          "counter": "upload_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 upload_document

What does the upload_document tool do? +

Copy a server-visible file into the upload area, then register and parse it. 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 upload_document? +

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

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

Can I rate-limit upload_document? +

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

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

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