backup_site · LocalWP MCP: Risk & Policy

WHAT IT DOES

What backup_site does on LocalWP MCP

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

The tool creates a new backup artifact (a reversible write operation). It does not delete or overwrite existing data, execute arbitrary code, or involve financial transactions. Severity is medium because creating backups consumes storage and could potentially expose sensitive site data if misused, but the action itself is non-destructive and reversible.

From the tool's definition Creates a Local-friendly backup for the selected site

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

backup_site Rate-limited

backup_site 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_site": {
      "limits": [
        {
          "counter": "backup_site_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 backup_site

What does the backup_site tool do? +

Creates a Local-friendly backup for the selected site. Use scope=. 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 backup_site? +

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

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

Can I rate-limit backup_site? +

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

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

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