// SCAN REPORT

Google Search Console Mcp Python

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

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

Last updated: 2 Jul 2026

2 can modify or destroy data

4 read-only

6 tools total

Community server · catalogue entry verified 02/07/2026

How to control Google Search Console Mcp Python ↓

TOOL MAP

What Google Search Console Mcp Python exposes to your agents

Read (4) 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 Mcp Python tools

Destructive · High delete_site Deleting a site from Google Search Console is an irreversible operation that removes all associated data, analytics, and configurations from the account. Write · Medium add_site This tool creates a new site resource in Google Search Console, which is a reversible Write operation.

2 of Google Search Console Mcp Python's 6 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 Mcp Python

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

Deny destructive operations

{
  "delete_site": {
    "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

{
  "add_site": {
    "limits": [
      {
        "counter": "add_site_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_site": {
    "limits": [
      {
        "counter": "get_site_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 Mcp Python — 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 MCP PYTHON →

Instant setup, no code required.

FULL CATALOGUE

All 6 Google Search Console Mcp Python tools

DESTRUCTIVE 1 tools

Destructive delete_site Remove a site from your Google Search Console account.

WRITE 1 tools

Write add_site Add a new site to your Google Search Console account.

READ 4 tools

Read get_site Get information about a specific site in Google Search Console. Read inspect_url inspect_url Read list_sites List all sites in your Google Search Console account. Read search_analytics search_analytics

EXPLORE

Related servers

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

FAQ

Questions about Google Search Console Mcp Python

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

Yes. The Google Search Console Mcp Python server exposes 1 destructive tools including delete_site. 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 Mcp Python? +

The Google Search Console Mcp Python server has 1 write tools including add_site. 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 Mcp Python.

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

6 tools across 3 categories: Destructive, Read, Write. 4 are read-only. 2 can modify, create, or delete data.

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

Register the Google Search Console Mcp Python 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 Mcp Python tool call.

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

ENFORCE POLICY ON GOOGLE SEARCH CONSOLE MCP PYTHON →

Instant setup, no code required.

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