scan_inbox · Scifinder Route MCP: Risk & Policy

WHAT IT DOES

What scan_inbox does on Scifinder Route

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

The tool scans for new files and registers/queues them in the system, which constitutes a write operation (creating new records/queue entries). It does not merely read — it actively modifies system state by registering files. No irreversible deletion or financial action is involved.

From the tool's definition scan inbox... queue/register new files

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

scan_inbox Rate-limited

scan_inbox 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": {
    "scan_inbox": {
      "limits": [
        {
          "counter": "scan_inbox_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 scan_inbox

What does the scan_inbox tool do? +

Scan the NAS inbox for supported SciFinder exports and queue/register new files. 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 scan_inbox? +

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

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

Can I rate-limit scan_inbox? +

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

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

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