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

google_ads_conversions_remove

Archive (status=REMOVED) a Google Ads conversion action.

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/google-ads-conversions-remove.md

What google_ads_conversions_remove does on Mureo

AI agents call google_ads_conversions_remove 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 google_ads_conversions_remove is rated Critical

Setting a conversion action to REMOVED status permanently disables it, which can disrupt conversion tracking across campaigns. While technically an archival state change rather than a hard delete, removing a conversion action in Google Ads is effectively irreversible in practice — reinstating it does not recover historical attribution data or restore active tracking.

From the tool's definition Archive (status=REMOVED) a Google Ads conversion action

Questions about google_ads_conversions_remove

What does the google_ads_conversions_remove tool do? +

Archive (status=REMOVED) a Google Ads conversion action. 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 google_ads_conversions_remove? +

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

google_ads_conversions_remove 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 google_ads_conversions_remove? +

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

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

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