google_ads_search_geo_targets
AI agents call google_ads_search_geo_targets 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 'search' prefix combined with 'geo_targets' strongly suggests data retrieval of geographic targeting options or information. No side effects are implied by the name. Despite the empty description reducing confidence slightly, the tool appears designed to query or list available geographic targets rather than modify campaign data. This aligns with Read category tools that support campaign management workflows.
From the tool's definition Tool name contains 'search' and 'geo_targets', suggesting it retrieves geographic targeting data for Google Ads campaigns.
Attacks that exploit this kind of access
google_ads_search_geo_targets. 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_search_geo_targets: 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_search_geo_targets 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_search_geo_targets 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_search_geo_targets. 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_search_geo_targets 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 →