google_ads_get_search_terms
AI agents call google_ads_get_search_terms to retrieve information from Google Ads MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix combined with 'search_terms' indicates a data retrieval operation. This would query historical search terms or performance data from Google Ads, returning information for analysis without modifying campaigns, keywords, or account state. Despite the empty description, the tool name itself provides strong evidence for Read classification.
From the tool's definition Tool name 'google_ads_get_search_terms' indicates retrieval of search term data. The verb 'get' is a classic Read operation pattern.
Attacks that exploit this kind of access
google_ads_get_search_terms. It is categorised as a Read tool in the Google Ads MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Google Ads MCP Server MCP server in PolicyLayer and add a rule for google_ads_get_search_terms: 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_get_search_terms 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 google_ads_get_search_terms 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_get_search_terms. 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_get_search_terms 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 →