meta_ads_catalogs_delete

THE RISK

Critical Risk

Why meta_ads_catalogs_delete needs a policy

This tool permanently removes a Product Catalog, which is an irreversible destructive action. Product catalogs are critical assets for Meta Ads campaigns—their deletion cannot be undone without manual recreation or restoration from backups. While not directly financial, the business impact is severe: campaigns relying on the deleted catalog will break, and recovery requires significant manual intervention.

From the tool's definition Tool name contains 'delete' and description states 'Deletes a Product Catalog' with irreversible effect. Deleting a product catalog removes advertising assets that cannot be trivially restored.

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

POLICY

How to control meta_ads_catalogs_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_catalogs_delete:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "meta_ads_catalogs_delete"
  ]
}

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

Create a free account and register Mureo — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Mureo tools

Financial google_ads_budget_reallocation Propose a budget reallocation plan by cutting up to 20% Financial meta_ads_instagram_boost Boosts an organic Instagram post by creating a paid ad Financial meta_ads_page_posts_boost Boosts an existing Facebook Page post by creating a paid Destructive google_ads_callouts_remove Detach a callout asset from a Google Ads campaign by Destructive google_ads_conversions_remove Archive (status=REMOVED) a Google Ads conversion action. Destructive google_ads_keywords_remove Removes (soft-deletes) a single keyword criterion from an ad Destructive google_ads_negative_keywords_remove Removes a single campaign-level negative keyword. Returns the Destructive google_ads_sitelinks_remove Detach a sitelink asset from a Google Ads campaign by

All 185 Mureo tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Mureo → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about meta_ads_catalogs_delete

What does the meta_ads_catalogs_delete tool do? +

Deletes a Product Catalog. 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_catalogs_delete? +

Register the Mureo MCP server in PolicyLayer and add a rule for meta_ads_catalogs_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_catalogs_delete? +

meta_ads_catalogs_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_catalogs_delete? +

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

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

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

CHECK YOUR STACK →