Deletes a saved audience. Args: - audience_id (string): Saved audience ID
AI agents call meta_delete_saved_audience 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.
Deletion of a saved audience cannot be undone and represents permanent removal of data. While the blast radius is limited to audience segments (not financial or system-critical), the irreversible nature of deletion places this in the Destructive category rather than Write.
From the tool's definition Tool name 'meta_delete_saved_audience' and description 'Deletes a saved audience' explicitly perform deletion, which is irreversible.
Documented attack patterns abuse exactly the kind of access meta_delete_saved_audience 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_saved_audience:
{
"version": "1",
"default": "deny",
"hide": [
"meta_delete_saved_audience"
]
} meta_delete_saved_audience 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 saved audience. Args: - audience_id (string): Saved audience ID. 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_saved_audience: 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_saved_audience 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_saved_audience 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_saved_audience. 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_saved_audience 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.