meta.campaigns.delete

DELETE a Meta campaign. Irreversible — historical insights stay accessible but the campaign disappears from Ads Manager. For temporary teardown prefer meta.campaigns.update with status=ARCHIVED. Dry-run by default; high-risk write.

Server Ads manlikemuneeb/ads-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What meta.campaigns.delete does on Ads

AI agents call meta.campaigns.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.

Why meta.campaigns.delete needs a policy

The tool permanently removes a Meta advertising campaign from Ads Manager, which cannot be undone. Although historical data is retained, the campaign itself is destroyed and cannot be restored. This matches the Destructive category definition ('irreversibly deletes or overwrites data, or actions that cannot be undone').

From the tool's definition Tool name contains 'delete'; description explicitly states 'DELETE a Meta campaign' and 'Irreversible — historical insights stay accessible but the campaign disappears from Ads Manager.' This is an irreversible deletion operation.

Questions about meta.campaigns.delete

What does the meta.campaigns.delete tool do? +

DELETE a Meta campaign. Irreversible — historical insights stay accessible but the campaign disappears from Ads Manager. For temporary teardown prefer meta.campaigns.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.

How do I enforce a policy on meta.campaigns.delete? +

Register the Ads MCP server in PolicyLayer and add a rule for meta.campaigns.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.

What risk level is meta.campaigns.delete? +

meta.campaigns.delete 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 meta.campaigns.delete? +

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

How do I block meta.campaigns.delete completely? +

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

What MCP server provides meta.campaigns.delete? +

meta.campaigns.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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.