query_search_analytics

Query Google Search Console search analytics data. Returns search queries, clicks, impressions, CTR, and average position.

Server Google Search Console lionkiii/google-searchconsole-mcp
Category Read
Risk class Low
Parameters 00 required

What query_search_analytics does on Google Search Console

AI agents call query_search_analytics to retrieve information from Google Search Console without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why query_search_analytics needs a policy

This tool only queries and retrieves existing search analytics data from Google Search Console. It has no side effects, does not modify any data, does not execute external operations, and does not involve financial transactions. The blast radius of misuse is minimal — an agent could only over-query or exfiltrate analytics already accessible to the authenticated account.

From the tool's definition Tool description states it 'Query[s] Google Search Console search analytics data' and 'Returns search queries, clicks, impressions, CTR, and average position' — purely retrieves analytics data with no modification, deletion, or execution capability.

Questions about query_search_analytics

What does the query_search_analytics tool do? +

Query Google Search Console search analytics data. Returns search queries, clicks, impressions, CTR, and average position. It is categorised as a Read tool in the Google Search Console MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on query_search_analytics? +

Register the Google Search Console 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. Nothing to install.

What risk level is query_search_analytics? +

query_search_analytics is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit query_search_analytics? +

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.

How do I block query_search_analytics completely? +

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.

What MCP server provides query_search_analytics? +

query_search_analytics is provided by the Google Search Console MCP server (lionkiii/google-searchconsole-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.