Return top queries from GSC by clicks.
AI agents call gsc_top_queries to retrieve information from SEO Analytics MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool fetches search performance metrics (top queries) from Google Search Console. It is a query operation that retrieves existing data without side effects. No data is modified, created, or deleted. The blast radius of misuse is minimal—an agent could only retrieve analytics data already accessible through the connected GSC account.
From the tool's definition Tool name 'gsc_top_queries' and description 'Return top queries from GSC by clicks' indicate retrieval of data. 'Return' and 'top queries' are read operations with no modification, creation, or deletion of data.
Attacks that exploit this kind of access
Return top queries from GSC by clicks. It is categorised as a Read tool in the SEO Analytics MCP MCP Server, which means it retrieves data without modifying state.
Register the SEO Analytics MCP server in PolicyLayer and add a rule for gsc_top_queries: 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 SEO Analytics MCP. Nothing to install.
gsc_top_queries 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_top_queries 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_top_queries. 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_top_queries is provided by the SEO Analytics MCP server (jafforgehq/google-analytics-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 →