Critical Risk →

meta_delete_adset

Deletes an ad set permanently. Args: - adset_id (string): Ad set ID to delete

How to control meta_delete_adset ↓

What meta_delete_adset does on Meta MCP Server

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

Critical Risk

Why meta_delete_adset needs a policy

This tool permanently deletes advertising campaign data that cannot be recovered. While not directly financial in nature, the destruction of ad sets could have significant business impact (loss of campaign configuration, historical performance data, and active advertising). It falls squarely into the Destructive category as the primary action is irreversible deletion.

From the tool's definition Tool name is 'meta_delete_adset' with description 'Deletes an ad set permanently.' The verb 'Deletes' combined with 'permanently' explicitly indicates irreversible removal of data.

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

How to control meta_delete_adset

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

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "meta_delete_adset"
  ]
}

meta_delete_adset disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

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

Free to start. No card required.

Related tools and policies

Go deeper

Questions about meta_delete_adset

What does the meta_delete_adset tool do? +

Deletes an ad set permanently. Args: - adset_id (string): Ad set 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 meta_delete_adset? +

Register the Meta MCP Server MCP server in PolicyLayer and add a rule for meta_delete_adset: 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 meta_delete_adset? +

meta_delete_adset 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_delete_adset? +

Yes. Add a rate_limit block to the meta_delete_adset 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_delete_adset completely? +

Set action: deny in the PolicyLayer policy for meta_delete_adset. 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_delete_adset? +

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

Free to start. No card required.

200 Meta MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.