gsc_site_detail
LIVE Google Search Console snapshot for ONE site: headline totals (clicks/impressions/CTR/avg position), top queries, top pages, and a daily trend. Data is fetched fresh from Google (not cached), so prefer a reasonable days window. The site must be GSC-bound (check gsc_sites → gscQueryable=true) ...
This record as markdown: /tools/a3plus-mcp/gsc-site-detail.md
What gsc_site_detail does on A3plus
AI agents call gsc_site_detail 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 window in days, 1-90, default 28. Ignored if startDate/endDate given. |
siteId | string | Yes | The A3Plus site ID from list_sites / gsc_sites. |
endDate | string | — | YYYY-MM-DD. |
topLimit | number | — | How many rows for the top queries / top pages breakdowns, 1-1000, default 25. |
startDate | string | — | YYYY-MM-DD. Use with endDate for an explicit window. |
Parameters from the server's own tool schema.
Why gsc_site_detail is rated Low
Even though gsc_site_detail 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_site_detail 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_site_detail, this is the rule to start with:
gsc_site_detail 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_site_detail call is checked against it from then on.
Questions about gsc_site_detail
LIVE Google Search Console snapshot for ONE site: headline totals (clicks/impressions/CTR/avg position), top queries, top pages, and a daily trend. Data is fetched fresh from Google (not cached), so prefer a reasonable days window. The site must be GSC-bound (check gsc_sites → gscQueryable=true) or this returns no_gsc_property. It is categorised as a Read tool in the A3plus MCP Server, which means it retrieves data without modifying state.
gsc_site_detail accepts 5 parameters: days, siteId, endDate, topLimit, startDate. 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_site_detail: 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_site_detail 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_site_detail 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_site_detail. 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_site_detail 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