wordpress_schedule_backups · WordPress MCP Server MCP

WHAT IT DOES

What wordpress_schedule_backups does on WordPress MCP Server

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

Scheduling backups creates or modifies backup job configurations, which is a reversible write operation. While backups themselves are protective, scheduling them modifies system state and automation rules. This is classified as Write rather than Read (it modifies configuration) or Destructive (backup scheduling is reversible).

From the tool's definition Tool name 'wordpress_schedule_backups' indicates creating or modifying backup schedule configurations. The description is empty, limiting evidence directly from the tool itself, but the sibling tools include 'wordpress_backup_database' and…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wordpress_schedule_backups Rate-limited

wordpress_schedule_backups 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_schedule_backups": {
      "limits": [
        {
          "counter": "wordpress_schedule_backups_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_schedule_backups

What does the wordpress_schedule_backups tool do? +

wordpress_schedule_backups. 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_schedule_backups? +

Register the WordPress MCP Server MCP server in PolicyLayer and add a rule for wordpress_schedule_backups: 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_schedule_backups? +

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

Can I rate-limit wordpress_schedule_backups? +

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

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

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