AI agents call suggest_brands to retrieve information from Google Ads without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The name 'suggest_brands' strongly implies a read/query operation that retrieves brand suggestions, similar to autocomplete or search functionality. No description is provided to confirm side effects. Given the context of a Google Ads MCP server, brand suggestions are typically a read operation. Confidence is lowered due to the empty description.
From the tool's definition Tool name 'suggest_brands' implies a suggestion/lookup operation; description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access suggest_brands gives an agent:
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 suggest_brands:
{
"version": "1",
"default": "deny",
"tools": {
"suggest_brands": {}
}
}suggest_brands is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
suggest_brands. It is categorised as a Read tool in the Google Ads MCP Server, which means it retrieves data without modifying state.
Register the Google Ads MCP server in PolicyLayer and add a rule for suggest_brands: 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.
suggest_brands is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the suggest_brands 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 suggest_brands. 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.
suggest_brands 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.
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.