wordpress_restore_backup · WordPress MCP Server MCP

WHAT IT DOES

What wordpress_restore_backup does on WordPress MCP Server

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

WHY IT NEEDS A POLICY

Why wordpress_restore_backup needs a policy

Restore operations modify site state by replacing current data with backup versions. This is Write rather than Destructive because restoration is itself reversible (you can restore a different backup or create new backups). However, confidence is tempered by the empty description—direct documentation would clarify scope (full site vs. selective restore) and any irreversibility constraints.

From the tool's definition Tool name 'wordpress_restore_backup' indicates restoration of backup data. Sibling context includes 'wordpress_backup_database' and 'wordpress_backup_files', establishing that backups are managed on this server.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wordpress_restore_backup Rate-limited

wordpress_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": {
    "wordpress_restore_backup": {
      "limits": [
        {
          "counter": "wordpress_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 WordPress MCP Server, so you can run agents against it safely.

FAQ

Questions about wordpress_restore_backup

What does the wordpress_restore_backup tool do? +

wordpress_restore_backup. It is categorised as a Write tool in the WordPress 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 wordpress_restore_backup? +

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

What risk level is wordpress_restore_backup? +

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

Can I rate-limit wordpress_restore_backup? +

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

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

wordpress_restore_backup is provided by the WordPress MCP Server MCP server (tonypepperwidow123-blip/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.