googleAds_remove_negative_keyword
Remove a negative keyword. Provide campaignId for campaign-level or adGroupId for ad-group-level.
This record as markdown: /tools/io-github-alifanov-scopegate/googleads-remove-negative-keyword.md
What googleAds_remove_negative_keyword does on ScopeGate
AI agents call googleAds_remove_negative_keyword 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_negative_keyword is rated Critical
Removing a negative keyword from a Google Ads campaign or ad group is a destructive action: once deleted, the keyword exclusion is gone and ads may immediately start matching previously blocked search queries, potentially driving unwanted spend. This is an irreversible modification to campaign targeting settings.
From the tool's definition 'Remove a negative keyword' — removing a negative keyword is an irreversible deletion that cannot be easily undone without knowing the prior state
Attacks that exploit this kind of access
The rule that runs googleAds_remove_negative_keyword safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScopeGate, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For googleAds_remove_negative_keyword, this is the rule to start with:
googleAds_remove_negative_keyword is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect ScopeGate, apply this rule, and every googleAds_remove_negative_keyword call is checked against it from then on.
Questions about googleAds_remove_negative_keyword
Remove a negative keyword. Provide campaignId for campaign-level or adGroupId for ad-group-level. 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.
Register the ScopeGate MCP server in PolicyLayer and add a rule for googleAds_remove_negative_keyword: 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.
googleAds_remove_negative_keyword 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 googleAds_remove_negative_keyword 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 googleAds_remove_negative_keyword. 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.
googleAds_remove_negative_keyword 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.
Across the catalogue