wp_cron_run · Wp Cli MCP: Risk & Policy

WHAT IT DOES

What wp_cron_run does on Wp Cli

AI agents invoke wp_cron_run to trigger actions in Wp Cli. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why wp_cron_run needs a policy

This tool executes code indirectly by triggering registered WordPress cron hooks. While the tool itself doesn't directly run arbitrary code, it invokes whatever callback functions are registered to the specified hook name.

From the tool's definition Tool name 'wp_cron_run' and description 'Manually trigger a specific WordPress cron event by its hook name' indicates execution of WordPress scheduled events based on user-supplied hook names.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wp_cron_run Rate-limited

wp_cron_run stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "wp_cron_run": {
      "limits": [
        {
          "counter": "wp_cron_run_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Wp Cli, so you can run agents against it safely.

FAQ

Questions about wp_cron_run

What does the wp_cron_run tool do? +

Manually trigger a specific WordPress cron event by its hook name. It is categorised as a Execute tool in the Wp Cli MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on wp_cron_run? +

Register the Wp Cli MCP server in PolicyLayer and add a rule for wp_cron_run: 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 Wp Cli. Nothing to install.

What risk level is wp_cron_run? +

wp_cron_run is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit wp_cron_run? +

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

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

wp_cron_run is provided by the Wp Cli MCP server (mvtandas/wp-cli-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.