restore_backup · LocalWP MCP: Risk & Policy

WHAT IT DOES

What restore_backup does on LocalWP MCP

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

WHY IT NEEDS A POLICY

Why restore_backup needs a policy

This tool overwrites site data and database state by applying a backup, which is a reversible modification operation (can be undone by restoring to a different backup or state). While it has significant blast radius due to potential data loss if applied to the wrong backup, it is reversible (unlike Destructive operations) and does not irreversibly delete data.

From the tool's definition Tool description states it 'Restores a LocalWP site from a .sql file or a backup_site directory' and 'can restore the database and...the backup'. The term 'restores' indicates overwriting/modifying existing site data and database content.

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

FAQ

Questions about restore_backup

What does the restore_backup tool do? +

Restores a LocalWP site from a .sql file or a backup_site directory. In full-access mode it can restore the database and, when available, the backup. It is categorised as a Write tool in the LocalWP MCP 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 LocalWP 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 LocalWP MCP. 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 LocalWP MCP server (kazimshah39/localwp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.