Query Google Search Console performance data (clicks, impressions, CTR, average position) for a site. Supports breakdown by query, page, country, device, search appearance, or date.
AI agents call query_search_analytics to retrieve information from Gsc Mcp Connector without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries existing performance metrics from Google Search Console without creating, modifying, deleting, or executing any operations. It is purely informational analysis of search performance data. The blast radius of misuse is low—an agent could over-query or analyze competitor data, but cannot alter GSC configuration, delete data, or trigger external operations.
From the tool's definition Tool description explicitly states it 'Query[s] Google Search Console performance data' with metrics like 'clicks, impressions, CTR, average position' and supports 'breakdown by query, page, country, device, search appearance, or date.' These are all…
Attacks that exploit this kind of access
Query Google Search Console performance data (clicks, impressions, CTR, average position) for a site. Supports breakdown by query, page, country, device, search appearance, or date. It is categorised as a Read tool in the Gsc Mcp Connector MCP Server, which means it retrieves data without modifying state.
Register the Gsc Mcp Connector MCP server in PolicyLayer and add a rule for query_search_analytics: 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 Gsc Mcp Connector. Nothing to install.
query_search_analytics 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 query_search_analytics 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 query_search_analytics. 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.
query_search_analytics is provided by the Gsc Mcp Connector MCP server (juju78/gsc-mcp-connector). 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 →