Analyse anonymous (hidden) query traffic that the GSC API cannot show. Reveals what percentage of your clicks come from queries Google redacts, and which pages get the most hidden traffic. Only possible with BigQuery bulk export.
AI agents call gsc_anonymous_traffic 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.
This tool queries and aggregates BigQuery data to surface analytics insights about hidden traffic patterns. It has no side effects—it does not create, modify, delete, or execute code/operations. The severity is low because reading analytics metadata poses minimal risk to system integrity or data security, even if misused by an AI agent.
From the tool's definition Tool performs analysis ('Analyse anonymous query traffic', 'Reveals what percentage', 'which pages get the most') of existing data without modifying, deleting, or executing external operations.
Documented attack patterns abuse exactly the kind of access gsc_anonymous_traffic 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_anonymous_traffic:
{
"version": "1",
"default": "deny",
"tools": {
"gsc_anonymous_traffic": {}
}
}gsc_anonymous_traffic is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Analyse anonymous (hidden) query traffic that the GSC API cannot show. Reveals what percentage of your clicks come from queries Google redacts, and which pages get the most hidden traffic. Only possible with BigQuery bulk export. It is categorised as a Read tool in the BigQuery MCP Server MCP Server, which means it retrieves data without modifying state.
Register the BigQuery MCP Server MCP server in PolicyLayer and add a rule for gsc_anonymous_traffic: 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.
gsc_anonymous_traffic 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_anonymous_traffic 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_anonymous_traffic. 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_anonymous_traffic 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.
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.