// SCAN REPORT

Google Search Console

13 tools. 0 can modify or destroy data without limits.

Read-only server. Low risk, but rate limits prevent runaway API costs.

Last updated: 29 Jun 2026

0 can modify or destroy data

13 read-only

13 tools total

Community server · catalogue entry verified 29/06/2026

How to control Google Search Console ↓

TOOL MAP

What Google Search Console exposes to your agents

Read (13) Write / Execute (0) Destructive / Financial (0)

Running more than one server? Check your whole stack →

THE RISK

What can go wrong

Even read-only tools carry cost. An agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up bills.

POLICY

How to control Google Search Console

PolicyLayer is an MCP gateway — it sits between your AI agents and Google Search Console, and nothing reaches the server without passing your rules. These are the rules we recommend:

Cap read operations

{
  "analyze_brand_queries": {
    "limits": [
      {
        "counter": "analyze_brand_queries_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Google Search Console — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON GOOGLE SEARCH CONSOLE →

Instant setup, no code required.

FULL CATALOGUE

All 13 Google Search Console tools

READ 13 tools

Read analyze_brand_queries Analyze branded vs non-branded search queries. Shows what percentage of traffic comes from brand searches. Read compare_performance Compare search performance between two time periods. Shows which queries/pages gained or lost traffic. Read export_analytics Export search analytics data as CSV or JSON format for external analysis or reporting. Read find_keyword_opportunities Find keyword optimization opportunities - queries with high impressions but low CTR that could be improved. Read get_keyword_trend Get the performance trend of a specific keyword over time. Shows daily clicks, impressions, and position chang Read get_top_pages Get top performing pages sorted by clicks, impressions, CTR, or position. Read inspect_url Inspect a URL to check its indexing status, mobile usability, and rich results. Shows if Google can crawl and Read list_accounts List all authenticated Google accounts and their associated GSC sites. Read list_sitemaps List all sitemaps submitted for a site in Google Search Console. Read list_sites List all sites you have access to in Google Search Console. When multiple accounts exist and no account is spe Read query_by_search_appearance Query analytics filtered by search appearance type (AMP, Rich Results, Video, FAQ, etc.). Read query_by_search_type Query analytics filtered by search type: web, image, video, news, or discover. Read query_search_analytics Query Google Search Console search analytics data. Returns search queries, clicks, impressions, CTR, and avera

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Google Search Console

Is the Google Search Console MCP server safe to use without restrictions? +

The Google Search Console server is primarily read-only with 13 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the Google Search Console MCP server expose? +

13 tools across 3 categories: Execute, Read, Write. 13 are read-only. 0 can modify, create, or delete data.

How do I enforce a policy on Google Search Console? +

Register the Google Search Console MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Google Search Console tool call.

Deterministic rules across all 13 Google Search Console tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON GOOGLE SEARCH CONSOLE →

Instant setup, no code required.

13 Google Search Console tools catalogued and risk-classified — across an index of 43,000+ MCP servers.