Delete a scheduled or draft post from PostEverywhere. This permanently removes the post and all its platform destinations. Cannot delete posts that have already been published. Use with caution as this action cannot be undone.
AI agents call delete_post to permanently remove resources in Posteverywhere — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool irreversibly deletes data (scheduled/draft posts and their configurations). While it cannot delete already-published posts, the permanent removal of draft content and associated metadata constitutes data destruction.
From the tool's definition "Delete a scheduled or draft post from PostEverywhere. This permanently removes the post and all its platform destinations." The description explicitly uses "permanently removes" and states "this action cannot be undone," which are hallmarks of destructive…
Attacks that exploit this kind of access
Delete a scheduled or draft post from PostEverywhere. This permanently removes the post and all its platform destinations. Cannot delete posts that have already been published. Use with caution as this action cannot be undone. It is categorised as a Destructive tool in the Posteverywhere MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Posteverywhere MCP server in PolicyLayer and add a rule for delete_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 Posteverywhere. Nothing to install.
delete_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 delete_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 delete_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.
delete_post is provided by the Posteverywhere MCP server (posteverywhere/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →