Find queries where mobile and desktop rank different pages from your site. This device cannibalisation is invisible in the GSC UI and impossible to detect via the API
AI agents call gsc_device_split 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 analyzes Search Console data to identify device-based ranking differences (device cannibalization). It performs no write operations, does not execute external commands, does not delete data, and does not involve financial transactions. It is purely a read operation that queries and reports on existing analytics data.
From the tool's definition Tool name 'gsc_device_split' and description 'Find queries where mobile and desktop rank different pages' indicates data retrieval and analysis.
Documented attack patterns abuse exactly the kind of access gsc_device_split 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_device_split:
{
"version": "1",
"default": "deny",
"tools": {
"gsc_device_split": {}
}
}gsc_device_split 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 queries where mobile and desktop rank different pages from your site. This device cannibalisation is invisible in the GSC UI and impossible to detect via the 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_device_split: 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_device_split 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_device_split 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_device_split. 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_device_split 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.