AI agents call gsc_query_search_analytics to retrieve information from Gsc 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. As part of a read-only server with no side effects, this is a Read category risk. Severity is low because it only retrieves analytics data without modifying or executing anything.
From the tool's definition Server is explicitly described as 'read-only tools' for 'querying Google Search Console data' including 'search analytics'. Tool name contains 'query_search_analytics' which is a retrieval operation. No write, delete, or execute operations are indicated.
Attacks that exploit this kind of access
gsc_query_search_analytics. It is categorised as a Read tool in the Gsc MCP Server, which means it retrieves data without modifying state.
Register the Gsc MCP server in PolicyLayer and add a rule for gsc_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. Nothing to install.
gsc_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 gsc_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 gsc_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.
gsc_query_search_analytics is provided by the Gsc MCP server (jayrockliffe-defused/gsc-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 →