New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

meta_ads_ad_rules_delete

Deletes an Automated Rule. Returns a success flag.

SERVERMureo SOURCElogly/mureo
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/logly-mureo/meta-ads-ad-rules-delete.md

What meta_ads_ad_rules_delete does on Mureo

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

Why meta_ads_ad_rules_delete is rated Critical

This tool permanently removes Meta Ads automated rules without reversibility. While not a direct financial transaction, deleting ad automation rules can have significant business impact by disrupting ongoing ad campaign management and optimization. This is categorized as Destructive rather than Write because deletion is irreversible and cannot be undone through the tool interface.

From the tool's definition Deletes an Automated Rule. The verb 'Deletes' and context of removing ad automation rules indicates irreversible removal of configuration.

Questions about meta_ads_ad_rules_delete

What does the meta_ads_ad_rules_delete tool do? +

Deletes an Automated Rule. 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_ad_rules_delete? +

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

meta_ads_ad_rules_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_ad_rules_delete? +

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

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

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

More on Mureo, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Mureo's. Pull the full record:

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.