Deletes a Custom Audience. Returns a success flag.
AI agents call meta_ads_audiences_delete to permanently remove resources in Mureo — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a Custom Audience in Meta Ads is an irreversible operation that destroys audience data and segments. This cannot be undone without manual recreation. While not directly financial, the audience asset has business value and improper deletion could disrupt ad campaigns and targeting strategies.
From the tool's definition Tool name explicitly states 'delete' and description confirms 'Deletes a Custom Audience' with irreversible effect. Returns success flag indicating action completion.
Documented attack patterns abuse exactly the kind of access meta_ads_audiences_delete gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mureo, and nothing reaches the server without passing your rules. This is the rule we recommend for meta_ads_audiences_delete:
{
"version": "1",
"default": "deny",
"hide": [
"meta_ads_audiences_delete"
]
}meta_ads_audiences_delete 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 Custom Audience. Returns a success flag. It is categorised as a Destructive tool in the Mureo MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mureo MCP server in PolicyLayer and add a rule for meta_ads_audiences_delete: 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 Mureo. Nothing to install.
meta_ads_audiences_delete 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_ads_audiences_delete 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_ads_audiences_delete. 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_ads_audiences_delete is provided by the Mureo MCP server (logly/mureo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mureo, 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.
185 Mureo tools catalogued and risk-classified — across an index of 43,000+ MCP servers.