googleAds_add_negative_keyword
Add a negative keyword. Provide campaignId for campaign-level or adGroupId for ad-group-level negative keyword.
This record as markdown: /tools/io-github-alifanov-scopegate/googleads-add-negative-keyword.md
What googleAds_add_negative_keyword does on ScopeGate
AI agents use googleAds_add_negative_keyword to create or update resources in ScopeGate, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ScopeGate environment.
Why googleAds_add_negative_keyword is rated Medium
This tool creates or modifies data in Google Ads (adding a negative keyword entry) without permanently deleting information. It is reversible—negative keywords can be removed. However, it affects advertising campaign behavior and budget allocation, which could impact business operations if misused by an agent.
From the tool's definition 'Add a negative keyword' - modifies ad campaign configuration by adding a negative keyword entry, which is a reversible change to Google Ads account structure.
Attacks that exploit this kind of access
The rule that runs googleAds_add_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_add_negative_keyword, this is the rule to start with:
googleAds_add_negative_keyword stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ScopeGate, apply this rule, and every googleAds_add_negative_keyword call is checked against it from then on.
Questions about googleAds_add_negative_keyword
Add a negative keyword. Provide campaignId for campaign-level or adGroupId for ad-group-level negative keyword. It is categorised as a Write tool in the ScopeGate MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ScopeGate MCP server in PolicyLayer and add a rule for googleAds_add_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_add_negative_keyword is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the googleAds_add_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_add_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_add_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.
This server
Across the catalogue