threads_delete_post

THE RISK

Critical Risk

Why threads_delete_post needs a policy

This tool removes content in an irreversible manner. Once a Threads post is deleted, it cannot be recovered. The blast radius depends on the post's visibility and engagement—deleting a popular or important post could significantly damage reputation or business operations. This is classified as Destructive rather than Write because the operation cannot be undone.

From the tool's definition The tool is called `threads_delete_post` with description 'Deletes a Threads post permanently.' The use of the words 'delete' and 'permanently' clearly indicates irreversible removal of data.

Documented attack patterns abuse exactly the kind of access threads_delete_post gives an agent:

POLICY

How to control threads_delete_post

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 threads_delete_post:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "threads_delete_post"
  ]
}

threads_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.

Create a free account and register Meta MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Meta MCP Server tools

Financial meta_create_adset Creates a new ad set within a campaign. Args: - ad_account_id (string): Ad account ID ( Financial meta_create_campaign Creates a new campaign in a Meta ad account. Args: - ad_account_id (string): Ad account Destructive meta_delete_ad Deletes an ad permanently. Args: - ad_id (string): Ad ID to delete Destructive meta_delete_ad_rule Deletes an automated ad rule. Args: - rule_id (string): Ad rule ID Destructive meta_delete_adset Deletes an ad set permanently. Args: - adset_id (string): Ad set ID to delete Destructive meta_delete_campaign Deletes (archives) a campaign. This cannot be undone. Args: - campaign_id (string): Cam Destructive meta_delete_comment Deletes a comment on a Facebook Page post. Permanent action. Args: - comment_id (string Destructive meta_delete_custom_audience Deletes a custom audience permanently. This cannot be undone. Args: - audience_id (stri

All 200 Meta MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Meta MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about threads_delete_post

What does the threads_delete_post tool do? +

Deletes a Threads post permanently. Args: - media_id (string): Threads media ID to delete. 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.

How do I enforce a policy on threads_delete_post? +

Register the Meta MCP Server MCP server in PolicyLayer and add a rule for threads_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.

What risk level is threads_delete_post? +

threads_delete_post is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit threads_delete_post? +

Yes. Add a rate_limit block to the threads_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.

How do I block threads_delete_post completely? +

Set action: deny in the PolicyLayer policy for threads_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.

What MCP server provides threads_delete_post? +

threads_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.

Enforce policy on every Meta MCP Server tool call.

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.

CHECK YOUR STACK →