searchConsole_query_analytics

Query search analytics data for a site

SERVERScopeGate SOURCEhttps://mcp.scopegate.cloud/{api_key}

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-alifanov-scopegate/searchconsole-query-analytics.md

WHAT IT DOES

What searchConsole_query_analytics does on ScopeGate

AI agents call searchConsole_query_analytics to retrieve information from ScopeGate without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why searchConsole_query_analytics is rated Low

This tool retrieves and queries analytics data without creating, modifying, or deleting any data. The blast radius of misuse is limited to unauthorized exposure of analytics insights, which is a read-level risk. The confidence is high because the language is explicit about querying (retrieval) rather than writing or executing arbitrary operations.

From the tool's definition The tool name includes 'query_analytics' and description states 'Query search analytics data for a site' — these are retrieval operations with no modification or destructive capability.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs searchConsole_query_analytics safely

PolicyLayer is an MCP gateway: it sits between your AI agents and ScopeGate, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For searchConsole_query_analytics, this is the rule to start with:

searchConsole_query_analytics Allowed

searchConsole_query_analytics is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "searchConsole_query_analytics": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect ScopeGate, apply this rule, and every searchConsole_query_analytics call is checked against it from then on.

FAQ

Questions about searchConsole_query_analytics

What does the searchConsole_query_analytics tool do? +

Query search analytics data for a site. It is categorised as a Read tool in the ScopeGate MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on searchConsole_query_analytics? +

Register the ScopeGate MCP server in PolicyLayer and add a rule for searchConsole_query_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 ScopeGate. Nothing to install.

What risk level is searchConsole_query_analytics? +

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

Can I rate-limit searchConsole_query_analytics? +

Yes. Add a rate_limit block to the searchConsole_query_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 searchConsole_query_analytics completely? +

Set action: deny in the PolicyLayer policy for searchConsole_query_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 searchConsole_query_analytics? +

searchConsole_query_analytics is provided by the ScopeGate MCP server (https://mcp.scopegate.cloud/{api_key}). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on ScopeGate, and thousands of servers like it.

This server

All 385 ScopeGate tools →

Across the catalogue

claude_query on Claude Bridge → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →