google_ads_remove_asset_from_group
AI agents call google_ads_remove_asset_from_group to permanently remove resources in Google Ads MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The word 'remove' in the tool name strongly suggests a destructive operation that detaches or deletes an asset from an asset group (likely a Performance Max asset group), which is typically irreversible without manual re-addition.
From the tool's definition Tool name: google_ads_remove_asset_from_group — 'remove' implies irreversible deletion of an asset from a group
Attacks that exploit this kind of access
google_ads_remove_asset_from_group. It is categorised as a Destructive tool in the Google Ads MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Google Ads MCP Server MCP server in PolicyLayer and add a rule for google_ads_remove_asset_from_group: 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 MCP Server. Nothing to install.
google_ads_remove_asset_from_group is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the google_ads_remove_asset_from_group 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.
Set action: deny in the PolicyLayer policy for google_ads_remove_asset_from_group. 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.
google_ads_remove_asset_from_group is provided by the Google Ads MCP Server MCP server (mikdeangelis/mcp-google-ads). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →