AI agents call query_search_analytics to retrieve information from Google Search Console MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool queries search analytics data from Google Search Console. This is a read-only operation that retrieves metrics and insights without creating, modifying, deleting, or executing external actions. The server description emphasizes 'querying', 'comparing performance', and 'identifying opportunities'—all analytical tasks. No evidence suggests mutation or side effects.
From the tool's definition Tool named 'query_search_analytics' with context of 'querying search analytics' from server description; sibling tools like 'get_search_trends', 'get_top_performing_content', and 'list_sites' all indicate data retrieval operations with no modifications.
Documented attack patterns abuse exactly the kind of access query_search_analytics gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Google Search Console MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for query_search_analytics:
{
"version": "1",
"default": "deny",
"tools": {
"query_search_analytics": {}
}
}query_search_analytics 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.
query_search_analytics. It is categorised as a Read tool in the Google Search Console MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Google Search Console MCP Server 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 Google Search Console MCP Server. 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 Google Search Console MCP Server MCP server (seotesting-com/gsc-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Google Search Console MCP Server, 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.
5 Google Search Console MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.