Year-over-year seasonal traffic analysis. Shows monthly clicks, impressions, CTR, and position with YoY comparison. Requires 12+ months of BigQuery data. Impossible with the 16-month rolling GSC API.
AI agents call gsc_seasonal 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.
The tool performs retrospective seasonal traffic analysis by querying BigQuery data to compute and display performance metrics. It has no side effects, does not create or modify data, does not execute external code, and does not delete or move money.
From the tool's definition Tool description states it 'Shows monthly clicks, impressions, CTR, and position with YoY comparison' — these are all read-only analytics queries that retrieve and analyze historical data without modifying, deleting, or executing operations.
Documented attack patterns abuse exactly the kind of access gsc_seasonal 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_seasonal:
{
"version": "1",
"default": "deny",
"tools": {
"gsc_seasonal": {}
}
}gsc_seasonal 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.
Year-over-year seasonal traffic analysis. Shows monthly clicks, impressions, CTR, and position with YoY comparison. Requires 12+ months of BigQuery data. Impossible with the 16-month rolling GSC API. 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_seasonal: 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_seasonal 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_seasonal 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_seasonal. 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_seasonal 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.