// SCAN REPORT

Google Search Console

7 tools. 2 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 29 Jun 2026

2 can modify or destroy data

5 read-only

7 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 (5) Write / Execute (1) Destructive / Financial (1)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Google Search Console tools

Destructive · High gsc_delete_sitemap Delete a sitemap from Google Search Console. Write · Medium gsc_submit_sitemap Submit a new sitemap to Google Search Console for crawling.

2 of Google Search Console's 7 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

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:

Deny destructive operations

{
  "gsc_delete_sitemap": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "gsc_submit_sitemap": {
    "limits": [
      {
        "counter": "gsc_submit_sitemap_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "gsc_get_sitemap": {
    "limits": [
      {
        "counter": "gsc_get_sitemap_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 7 Google Search Console tools

DESTRUCTIVE 1 tools

Destructive gsc_delete_sitemap Delete a sitemap from Google Search Console.

WRITE 1 tools

Write gsc_submit_sitemap Submit a new sitemap to Google Search Console for crawling.

READ 5 tools

Read gsc_get_sitemap Get detailed information about a specific sitemap. Read gsc_inspect_url Inspect a URL to get its indexing status in Google Search. Returns index status, crawl information, mobile usa Read gsc_list_sitemaps List all sitemaps submitted for a site in Google Search Console. Read gsc_list_sites List all sites (properties) you have access to in Google Search Console. Returns site URLs and permission leve Read gsc_search_analytics Query search analytics data from Google Search Console. Get clicks, impressions, CTR, and position data. You c

EXPLORE

Related servers

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

FAQ

Questions about Google Search Console

Can an AI agent delete data through the Google Search Console MCP server? +

Yes. The Google Search Console server exposes 1 destructive tools including gsc_delete_sitemap. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Google Search Console? +

The Google Search Console server has 1 write tools including gsc_submit_sitemap. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Google Search Console.

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

7 tools across 3 categories: Destructive, Read, Write. 5 are read-only. 2 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 7 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.

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