gsc_search_analytics
Flexible LIVE Search Console query for one site — the escape hatch when gsc_site_detail isn't the breakdown you need. You pick the dimensions (≤3 of query, page, country, device, date, searchAppearance) and the window. Example: dimensions=["query","country"] to see which countries each keyword ra...
This record as markdown: /tools/a3plus-mcp/gsc-search-analytics.md
What gsc_search_analytics does on A3plus
AI agents call gsc_search_analytics to retrieve information from A3plus without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
days | number | — | Lookback 1-90, default 28 (ignored if startDate given). |
limit | number | — | Rows to return, 1-1000, default 100. |
offset | number | — | startRow into the result set, default 0. |
siteId | string | Yes | The A3Plus site ID. |
endDate | string | — | YYYY-MM-DD. |
startDate | string | — | YYYY-MM-DD (with endDate). |
dimensions | array | — | Up to 3 GSC dimensions. Default ["query"]. |
Parameters from the server's own tool schema.
Why gsc_search_analytics is rated Low
Even though gsc_search_analytics only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs gsc_search_analytics safely
PolicyLayer is an MCP gateway: it sits between your AI agents and A3plus, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gsc_search_analytics, this is the rule to start with:
gsc_search_analytics is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect A3plus, apply this rule, and every gsc_search_analytics call is checked against it from then on.
Questions about gsc_search_analytics
Flexible LIVE Search Console query for one site — the escape hatch when gsc_site_detail isn't the breakdown you need. You pick the dimensions (≤3 of query, page, country, device, date, searchAppearance) and the window. Example: dimensions=["query","country"] to see which countries each keyword ranks in. It is categorised as a Read tool in the A3plus MCP Server, which means it retrieves data without modifying state.
gsc_search_analytics accepts 7 parameters: days, limit, offset, siteId, endDate, startDate, dimensions. Required: siteId. The full parameter table on this page comes from the server's own tool schema.
Register the A3plus MCP server in PolicyLayer and add a rule for gsc_search_analytics: 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 A3plus. Nothing to install.
gsc_search_analytics 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_search_analytics 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_search_analytics. 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_search_analytics is provided by the A3plus MCP server (a3plus-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on A3plus, and thousands of servers like it.
This server
Across the catalogue