Return query+page combinations from GSC for intent/page matching analysis.
AI agents call gsc_query_page_pairs 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 retrieves and queries existing search performance data from GSC without creating, modifying, deleting, or executing operations. It is purely analytical—returning combinations for analysis purposes. No reversible or irreversible modifications occur, nor are external operations triggered.
From the tool's definition The tool 'gsc_query_page_pairs' returns query+page combinations from Google Search Console for intent/page matching analysis. The verb 'Return' and the analytical context (intent/page matching) indicate data retrieval with no side effects.
Attacks that exploit this kind of access
Return query+page combinations from GSC for intent/page matching analysis. 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_query_page_pairs: 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_query_page_pairs 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_page_pairs 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_page_pairs. 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_page_pairs 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 →