googleAds_remove_extension

Remove (unlink) a sitelink or callout extension from a campaign or account

SERVERScopeGate SOURCEhttps://mcp.scopegate.cloud/{api_key}
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/io-github-alifanov-scopegate/googleads-remove-extension.md

What googleAds_remove_extension does on ScopeGate

AI agents call googleAds_remove_extension to permanently remove resources in ScopeGate, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why googleAds_remove_extension is rated Critical

Removing/unlinking an ad extension from a campaign or account is effectively irreversible without manual reconfiguration—once unlinked, the extension stops serving and the association is deleted. This constitutes a destructive action with high blast radius since it directly impacts live advertising campaigns, potentially reducing ad performance and visibility immediately.

From the tool's definition Remove (unlink) a sitelink or callout extension from a campaign or account

Questions about googleAds_remove_extension

What does the googleAds_remove_extension tool do? +

Remove (unlink) a sitelink or callout extension from a campaign or account. It is categorised as a Destructive tool in the ScopeGate 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 googleAds_remove_extension? +

Register the ScopeGate MCP server in PolicyLayer and add a rule for googleAds_remove_extension: 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 ScopeGate. Nothing to install.

What risk level is googleAds_remove_extension? +

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

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

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

googleAds_remove_extension is provided by the ScopeGate MCP server (https://mcp.scopegate.cloud/{api_key}). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on ScopeGate, 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 ScopeGate'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.