Critical Risk →

meta_ads_products_delete

Deletes a single catalog product. Returns a success flag.

How to control meta_ads_products_delete ↓

What meta_ads_products_delete does on Mureo

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

Critical Risk

Why meta_ads_products_delete needs a policy

Deletion of catalog products is an irreversible action that cannot be undone without manual restoration. This constitutes a destructive operation with potential business impact (lost product listings, disrupted ad campaigns).

From the tool's definition Tool name explicitly states 'delete' and description confirms 'Deletes a single catalog product' with irreversible effect. Returns success flag indicating the deletion is committed.

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

How to control meta_ads_products_delete

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

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

meta_ads_products_delete 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 Mureo — 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_ads_products_delete

What does the meta_ads_products_delete tool do? +

Deletes a single catalog product. 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.

How do I enforce a policy on meta_ads_products_delete? +

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

What risk level is meta_ads_products_delete? +

meta_ads_products_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_ads_products_delete? +

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

Set action: deny in the PolicyLayer policy for meta_ads_products_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_ads_products_delete? +

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

Enforce policy on every Mureo tool call.

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.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.