backup_database · Scifinder Route MCP: Risk & Policy

WHAT IT DOES

What backup_database does on Scifinder Route

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

Backup creation is fundamentally a write operation—it produces a new artifact (the backup file) without destructive or irreversible changes to existing data. While backups are typically safe operations, they do involve writing data to storage. The severity is low because backups are non-destructive, non-executable, and do not compromise system integrity or enable data loss when used as designed.

From the tool's definition Tool description states 'Create a SQLite database backup, or report Postgres backup guidance.' The action is creating a backup file, which is a write operation that creates new data (a backup artifact) without deleting or modifying the original database.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

backup_database Rate-limited

backup_database 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": {
    "backup_database": {
      "limits": [
        {
          "counter": "backup_database_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 backup_database

What does the backup_database tool do? +

Create a SQLite database backup, or report Postgres backup guidance. 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 backup_database? +

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

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

Can I rate-limit backup_database? +

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

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

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