restore_backup · File Patch MCP Server MCP: Risk & Policy

WHAT IT DOES

What restore_backup does on File Patch MCP Server

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

WHY IT NEEDS A POLICY

Why restore_backup needs a policy

This tool modifies files by restoring them from backup, which is a Write operation (reversible modification of data). While it involves recovery/rollback semantics, the primary action is writing a file's content to a previous state. This is not Destructive because the original modified file isn't irreversibly deleted—it can typically be backed up again.

From the tool's definition Tool name 'restore_backup' and description 'Restore a file from backup' indicate this tool restores/recovers a file from a previously saved backup state, which modifies the current file to a prior version.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

restore_backup Rate-limited

restore_backup 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": {
    "restore_backup": {
      "limits": [
        {
          "counter": "restore_backup_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 File Patch MCP Server, so you can run agents against it safely.

FAQ

Questions about restore_backup

What does the restore_backup tool do? +

Restore a file from backup. It is categorised as a Write tool in the File Patch MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on restore_backup? +

Register the File Patch MCP Server MCP server in PolicyLayer and add a rule for restore_backup: 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 File Patch MCP Server. Nothing to install.

What risk level is restore_backup? +

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

Can I rate-limit restore_backup? +

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

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

restore_backup is provided by the File Patch MCP Server MCP server (shenning00/patch_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.