Schedule a WordPress post for future publication
AI agents use schedule-post to create or update resources in AutoWP MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AutoWP MCP Server environment.
Scheduling a post modifies post metadata (publication time) and triggers WordPress workflows, but does not permanently destroy data or execute arbitrary code. The action is reversible: the schedule can be changed or cancelled before publication.
From the tool's definition Tool name 'schedule-post' and description 'Schedule a WordPress post for future publication' indicate the creation or modification of post publishing metadata without permanent deletion.
Documented attack patterns abuse exactly the kind of access schedule-post gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AutoWP MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for schedule-post:
{
"version": "1",
"default": "deny",
"tools": {
"schedule-post": {
"limits": [
{
"counter": "schedule-post_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}schedule-post 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.
Free to start. No card required.
Schedule a WordPress post for future publication. It is categorised as a Write tool in the AutoWP MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AutoWP MCP Server MCP server in PolicyLayer and add a rule for schedule-post: 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 AutoWP MCP Server. Nothing to install.
schedule-post is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the schedule-post 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 schedule-post. 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.
schedule-post is provided by the AutoWP MCP Server MCP server (njengah/autowpmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AutoWP MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
47 AutoWP MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.