mcp_run_action_scheduler
Run due (past-due pending) Action Scheduler actions now through Action Scheduler
This record as markdown: /tools/io-github-cvrt-jh-wordpress-mcp/mcp-run-action-scheduler.md
What mcp_run_action_scheduler does on Wordpress
AI agents invoke mcp_run_action_scheduler to trigger actions in Wordpress. 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 mcp_run_action_scheduler is rated High
Triggers execution of scheduled WordPress actions with effects depending on queued task arguments.
From the tool's definition Run due Action Scheduler actions now through Action Scheduler
Attacks that exploit this kind of access
The rule that runs mcp_run_action_scheduler safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Wordpress, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mcp_run_action_scheduler, this is the rule to start with:
mcp_run_action_scheduler 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Wordpress, apply this rule, and every mcp_run_action_scheduler call is checked against it from then on.
Questions about mcp_run_action_scheduler
Run due (past-due pending) Action Scheduler actions now through Action Scheduler. It is categorised as a Execute tool in the Wordpress MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Wordpress MCP server in PolicyLayer and add a rule for mcp_run_action_scheduler: 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. Nothing to install.
mcp_run_action_scheduler 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 mcp_run_action_scheduler 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 mcp_run_action_scheduler. 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.
mcp_run_action_scheduler is provided by the Wordpress MCP server (@cavort-it-systems/wordpress-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Wordpress, and thousands of servers like it.
Across the catalogue