Critical Risk →

remove_asset_group_signal

Remove an asset group signal.

How to control remove_asset_group_signal ↓

What remove_asset_group_signal does on Google Ads

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

Critical Risk

Why remove_asset_group_signal needs a policy

The 'remove' operation on an asset group signal is an irreversible deletion action within the Google Ads API. Once removed, the signal is gone and must be recreated if needed. This is destructive rather than simply Write (which would be reversible updates).

From the tool's definition Tool name is 'remove_asset_group_signal' which uses the verb 'remove'; combined with the server's purpose to manage Google Ads campaigns, asset group signals, and the context of sibling tools that create/assign/manage ad resources, this removes an advertising…

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

How to control remove_asset_group_signal

PolicyLayer is an MCP gateway — it sits between your AI agents and Google Ads, and nothing reaches the server without passing your rules. This is the rule we recommend for remove_asset_group_signal:

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

remove_asset_group_signal 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 Google Ads — 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 remove_asset_group_signal

What does the remove_asset_group_signal tool do? +

Remove an asset group signal. It is categorised as a Destructive tool in the Google Ads 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 remove_asset_group_signal? +

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

What risk level is remove_asset_group_signal? +

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

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

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

remove_asset_group_signal is provided by the Google Ads MCP server (promobase/google-ads-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Google Ads tool call.

Start from Google Ads, 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.

59 Google Ads 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.