Landing pages with BOTH search performance (clicks, impressions, position from GSC) AND engagement data (sessions, engagement rate, conversions from GA4) side by side. Requires GA4 BigQuery export.
AI agents call ga4_gsc_page_performance 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 retrieves and displays analytics data combining Google Search Console and GA4 metrics. It queries existing data for reporting purposes with no side effects, modifications, or destructive operations. It is purely a read/query operation.
From the tool's definition Landing pages with BOTH search performance (clicks, impressions, position from GSC) AND engagement data (sessions, engagement rate, conversions from GA4) side by side
Documented attack patterns abuse exactly the kind of access ga4_gsc_page_performance 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 ga4_gsc_page_performance:
{
"version": "1",
"default": "deny",
"tools": {
"ga4_gsc_page_performance": {}
}
}ga4_gsc_page_performance 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.
Landing pages with BOTH search performance (clicks, impressions, position from GSC) AND engagement data (sessions, engagement rate, conversions from GA4) side by side. Requires GA4 BigQuery 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 ga4_gsc_page_performance: 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.
ga4_gsc_page_performance 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 ga4_gsc_page_performance 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 ga4_gsc_page_performance. 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.
ga4_gsc_page_performance 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.