backup_database · PySqlit MCP: Risk & Policy

WHAT IT DOES

What backup_database does on PySqlitMCP

AI agents use backup_database to create or update resources in PySqlitMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your PySqlitMCP environment.

WHY IT NEEDS A POLICY

Why backup_database needs a policy

Backup creates a new file containing a copy of database state, which is a reversible write operation. It does not destroy original data (not Destructive), does not execute arbitrary code (not Execute), and does not move money (not Financial). While backups are typically safe operations, misuse could include creating backups to exfiltrate sensitive data or overwriting existing backup files, hence medium severity.

From the tool's definition Tool performs 'backup_database' operation that exports/saves database state to a specified file. Server description states 'backup/restore' functionality as a core feature.

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 PySqlitMCP, so you can run agents against it safely.

FAQ

Questions about backup_database

What does the backup_database tool do? +

备份数据库到指定文件. It is categorised as a Write tool in the PySqlitMCP 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 PySqlit 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 PySqlitMCP. 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 PySqlit MCP server (python51888/pysqlitmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.