AI agents call delete_post to permanently remove resources in Facebook MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes content from a Facebook Page and cannot be undone through normal means. Deletion of published posts is an irreversible action with significant blast radius—an AI agent with misuse potential could remove critical business communications, announcements, or customer engagement content.
From the tool's definition Tool name is 'delete_post' and description states 'Deletes a post from the Facebook Page.' The verb 'deletes' combined with the action target 'post' directly indicates irreversible removal of data.
Documented attack patterns abuse exactly the kind of access delete_post gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Facebook MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_post:
{
"version": "1",
"default": "deny",
"hide": [
"delete_post"
]
}delete_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.
Deletes a post from the Facebook Page. It is categorised as a Destructive tool in the Facebook MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Facebook MCP Server 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 Facebook MCP Server. 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 Facebook MCP Server MCP server (tiroshanm/facebook-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 7 Facebook MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
7 Facebook MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.