AI agents call trash-post to permanently remove resources in AutoWP MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Moving a post to trash is a destructive operation: it removes the post from the site immediately. While WordPress trash does allow recovery within a retention window, the action is not easily reversible by an AI agent acting autonomously, and bulk or accidental trashing could cause significant content loss.
From the tool's definition 'Move a WordPress post to trash' — trashing a post removes it from public view and is effectively a deletion action (WordPress trash is a soft-delete that can be auto-purged)
Documented attack patterns abuse exactly the kind of access trash-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 trash-post:
{
"version": "1",
"default": "deny",
"hide": [
"trash-post"
]
} trash-post disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Move a WordPress post to trash. It is categorised as a Destructive tool in the AutoWP MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the AutoWP MCP Server MCP server in PolicyLayer and add a rule for trash-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.
trash-post is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the trash-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 trash-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.
trash-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.