wordpress_run_cron · WordPress MCP Server MCP: Risk & Policy

WHAT IT DOES

What wordpress_run_cron does on WordPress MCP Server

AI agents invoke wordpress_run_cron to trigger actions in WordPress MCP Server. 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 wordpress_run_cron needs a policy

Running cron jobs executes code whose effects depend on what cron tasks are registered in the WordPress instance. While not inherently destructive, cron execution can modify data, trigger external API calls, send emails, or perform side effects beyond the caller's direct control. This qualifies as Execute rather than Write because cron triggers indirect code execution.

From the tool's definition Tool named 'wordpress_run_cron' with empty description. The name indicates triggering WordPress cron jobs, which execute scheduled code/tasks.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wordpress_run_cron Rate-limited

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

FAQ

Questions about wordpress_run_cron

What does the wordpress_run_cron tool do? +

wordpress_run_cron. It is categorised as a Execute tool in the WordPress MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on wordpress_run_cron? +

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

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

Can I rate-limit wordpress_run_cron? +

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

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

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