AI agents call gsc.search_analytics.query to retrieve information from Ads without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical search analytics data from Google Search Console without creating, modifying, or deleting any data. It has no side effects and poses minimal risk even if misused by an AI agent, as it only surfaces existing performance metrics. The 'query' action is inherently read-only in this context.
From the tool's definition Tool name 'query' combined with description 'Query Search Console search analytics: clicks, impressions, CTR, position' indicates data retrieval only. The metrics listed (clicks, impressions, CTR, position) are analytics data with no modification capability.
Attacks that exploit this kind of access
Query Search Console search analytics: clicks, impressions, CTR, position by query / page / country / device / etc. It is categorised as a Read tool in the Ads MCP Server, which means it retrieves data without modifying state.
Register the Ads MCP server in PolicyLayer and add a rule for gsc.search_analytics.query: 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 Ads. Nothing to install.
gsc.search_analytics.query 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 gsc.search_analytics.query 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 gsc.search_analytics.query. 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.
gsc.search_analytics.query is provided by the Ads MCP server (manlikemuneeb/ads-mcp). 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 →