Find pages with consistent traffic decline over three consecutive months from GSC bulk export data. One bad month is noise; three is a problem.
AI agents call gsc_content_decay 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 reads and analyzes existing GSC export data to identify pages with declining search traffic patterns. It is a pure read operation that queries historical metrics to provide insights and recommendations, with no capability to modify data, execute external operations, or create side effects.
From the tool's definition Tool performs analysis of historical traffic data from Google Search Console (GSC) bulk export. Verbs and context indicate data retrieval and trend analysis: 'find pages', 'traffic decline', 'from GSC bulk export data'.
Documented attack patterns abuse exactly the kind of access gsc_content_decay 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_content_decay:
{
"version": "1",
"default": "deny",
"tools": {
"gsc_content_decay": {}
}
}gsc_content_decay 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.
Find pages with consistent traffic decline over three consecutive months from GSC bulk export data. One bad month is noise; three is a problem. 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_content_decay: 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_content_decay 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_content_decay 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_content_decay. 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_content_decay 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.