AI agents use restore-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.
This tool modifies data state reversibly by recovering a post from trash. It does not permanently delete data (which would be Destructive) nor execute arbitrary code (which would be Execute). It is a Write operation because it changes post status/metadata. Severity is medium because restoring a post could unintentionally republish content, but the action is reversible—the post can be deleted again.
From the tool's definition Tool name: 'restore-post'; description: 'Restore a WordPress post from trash'. The action restores (recovers) a previously deleted post, modifying its status from trash to published/draft state.
Documented attack patterns abuse exactly the kind of access restore-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 restore-post:
{
"version": "1",
"default": "deny",
"tools": {
"restore-post": {
"limits": [
{
"counter": "restore-post_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}restore-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.
Restore a WordPress post from trash. 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 restore-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.
restore-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 restore-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 restore-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.
restore-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.