DELETE a Meta ad set. Irreversible. For temporary teardown prefer meta.adsets.update with status=ARCHIVED. Dry-run by default; high-risk write.
AI agents call meta.adsets.delete to permanently remove resources in Ads — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool permanently deletes a Meta ad set with no undo capability. This is explicitly described as 'Irreversible' and categorized by the server as a 'high-risk write.' Deletion of advertising assets is a destructive operation that cannot be reversed, exceeding a simple write operation. The description explicitly recommends using archival as an alternative, confirming the irreversible nature.
From the tool's definition DELETE a Meta ad set. Irreversible.
Attacks that exploit this kind of access
DELETE a Meta ad set. Irreversible. For temporary teardown prefer meta.adsets.update with status=ARCHIVED. Dry-run by default; high-risk write. It is categorised as a Destructive tool in the Ads MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Ads MCP server in PolicyLayer and add a rule for meta.adsets.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 Ads. Nothing to install.
meta.adsets.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.adsets.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.adsets.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.adsets.delete is provided by the Ads MCP server (manlikemuneeb/ads-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →