Get Google Search Console search analytics data
AI agents call gsc_search_analytics to retrieve information from MCP Search Analytics Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries existing analytics data from Google Search Console without creating, modifying, deleting, or executing any external operations. It is a straightforward read operation with no side effects. Severity is low because even if an AI agent queries this data excessively, the blast radius is limited to data retrieval; no business-critical systems are affected.
From the tool's definition Tool description states 'Get Google Search Console search analytics data' — a retrieval operation with no modification capability.
Attacks that exploit this kind of access
Get Google Search Console search analytics data. It is categorised as a Read tool in the MCP Search Analytics Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Search Analytics Server MCP server in PolicyLayer and add a rule for gsc_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 MCP Search Analytics Server. Nothing to install.
gsc_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 gsc_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 gsc_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.
gsc_search_analytics is provided by the MCP Search Analytics Server MCP server (vesivanov/mcp-search-analytics). 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 →