Deletes a post from a Facebook Page. This action is permanent and cannot be undone. Args: - post_id (string): The post ID to delete (format: {page_id}_{post_id}) - page_id (string): The Page ID (for authentication)
AI agents call meta_delete_post to permanently remove resources in Meta MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool irreversibly deletes data (a published post). Once executed, the action cannot be reversed. This matches the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone.' The severity is high because unintended deletion of legitimate business content (e.g., important announcements, customer engagement posts) could cause reputational damage, loss of engagement…
From the tool's definition Description explicitly states 'Deletes a post' and 'This action is permanent and cannot be undone.' The tool accepts post_id and page_id arguments to identify and remove content.
Documented attack patterns abuse exactly the kind of access meta_delete_post gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Meta MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for meta_delete_post:
{
"version": "1",
"default": "deny",
"hide": [
"meta_delete_post"
]
}meta_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 a Facebook Page. This action is permanent and cannot be undone. Args: - post_id (string): The post ID to delete (format: {page_id}_{post_id}) - page_id (string): The Page ID (for authentication). It is categorised as a Destructive tool in the Meta MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Meta MCP Server MCP server in PolicyLayer and add a rule for meta_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 Meta MCP Server. Nothing to install.
meta_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 meta_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 meta_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.
meta_delete_post is provided by the Meta MCP Server MCP server (oliverames/meta-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Meta 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.
200 Meta MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.