googleAds_dismiss_recommendation
Dismiss a Google Ads optimization recommendation
This record as markdown: /tools/io-github-alifanov-scopegate/googleads-dismiss-recommendation.md
What googleAds_dismiss_recommendation does on ScopeGate
AI agents use googleAds_dismiss_recommendation 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_dismiss_recommendation is rated Medium
Dismissing a recommendation modifies its state within Google Ads but does not delete data, spend money, or execute code. It is a reversible write action. Severity is medium because misuse could suppress valid optimization suggestions that affect campaign performance, but financial impact is indirect.
From the tool's definition 'Dismiss a Google Ads optimization recommendation' — dismissing a recommendation is a reversible state change (it can typically be un-dismissed or re-triggered) that modifies the status of a recommendation object
Attacks that exploit this kind of access
The rule that runs googleAds_dismiss_recommendation 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_dismiss_recommendation, this is the rule to start with:
googleAds_dismiss_recommendation 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_dismiss_recommendation call is checked against it from then on.
Questions about googleAds_dismiss_recommendation
Dismiss a Google Ads optimization recommendation. 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_dismiss_recommendation: 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_dismiss_recommendation 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_dismiss_recommendation 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_dismiss_recommendation. 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_dismiss_recommendation 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