Low Risk

gsc_site_snapshot

Get a quick overview of how the site is performing. Returns total clicks, impressions, CTR, position, unique pages and queries with a comparison to the prior period.

How to control gsc_site_snapshot ↓

AI agents call gsc_site_snapshot to retrieve information from BigQuery MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool queries and retrieves pre-computed analytics data (clicks, impressions, CTR, position metrics) from Google Search Console. It performs no side effects, does not modify data, execute code, delete records, or commit financial transactions. It is a straightforward read operation typical of analytics dashboard queries.

From the tool's definition Tool description states it 'Get[s] a quick overview' and 'Returns total clicks, impressions, CTR, position, unique pages and queries' — purely retrieval of aggregated analytics metrics with no modification, deletion, or execution capability.

Documented attack patterns abuse exactly the kind of access gsc_site_snapshot gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and BigQuery MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for gsc_site_snapshot:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "gsc_site_snapshot": {}
  }
}

gsc_site_snapshot is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register BigQuery MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the gsc_site_snapshot tool do? +

Get a quick overview of how the site is performing. Returns total clicks, impressions, CTR, position, unique pages and queries with a comparison to the prior period. It is categorised as a Read tool in the BigQuery MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on gsc_site_snapshot? +

Register the BigQuery MCP Server MCP server in PolicyLayer and add a rule for gsc_site_snapshot: 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 BigQuery MCP Server. Nothing to install.

What risk level is gsc_site_snapshot? +

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

Can I rate-limit gsc_site_snapshot? +

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

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

gsc_site_snapshot is provided by the BigQuery MCP Server MCP server (suganthan-mohanadasan/suganthans-bigquery-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every BigQuery MCP Server tool call.

Deterministic rules across all 32 BigQuery MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

32 BigQuery MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.