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.
Cron execution is an Execute category action: it triggers code/operations whose effects depend on what jobs are queued in WordPress. While cron jobs themselves are typically user-defined and legitimate, an AI agent could abuse this to trigger malicious tasks, spam operations, or denial-of-service. The empty description reduces confidence slightly, but the name and context clearly indicate execution capability.
From the tool's definition Tool name is 'wordpress_run_cron' with empty description. The 'run' verb combined with WordPress cron context indicates execution of scheduled tasks or trigger of time-based operations.
Documented attack patterns abuse exactly the kind of access wordpress_run_cron gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and WordPress MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for wordpress_run_cron:
{
"version": "1",
"default": "deny",
"tools": {
"wordpress_run_cron": {
"limits": [
{
"counter": "wordpress_run_cron_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
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.
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.
wordpress_run_cron is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
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.
wordpress_run_cron is provided by the WordPress MCP Server MCP server (raheesahmed/wordpress-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 190 WordPress MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
190 WordPress MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.