Low Risk

list_gsc_sites

List all sites verified in Google Search Console.

How to control list_gsc_sites ↓

AI agents call list_gsc_sites to retrieve information from Google Search Console MCP Intel Engine without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool retrieves and enumerates existing site configurations from Google Search Console. It performs a query operation with no side effects, no code execution, no data modification, and no resource deletion. The worst-case misuse would be an agent discovering which sites are verified, which is low-risk information exposure within the user's own account. This clearly falls under the Read category with low severity.

From the tool's definition Tool name 'list_gsc_sites' and description 'List all sites verified in Google Search Console' indicate a retrieval operation with no data modification or destructive capability.

Documented attack patterns abuse exactly the kind of access list_gsc_sites gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Google Search Console MCP Intel Engine, and nothing reaches the server without passing your rules. This is the rule we recommend for list_gsc_sites:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_gsc_sites": {}
  }
}

list_gsc_sites is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Google Search Console MCP Intel Engine — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the list_gsc_sites tool do? +

List all sites verified in Google Search Console. It is categorised as a Read tool in the Google Search Console MCP Intel Engine MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_gsc_sites? +

Register the Google Search Console MCP Intel Engine MCP server in PolicyLayer and add a rule for list_gsc_sites: 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 Google Search Console MCP Intel Engine. Nothing to install.

What risk level is list_gsc_sites? +

list_gsc_sites is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_gsc_sites? +

Yes. Add a rate_limit block to the list_gsc_sites 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.

How do I block list_gsc_sites completely? +

Set action: deny in the PolicyLayer policy for list_gsc_sites. 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.

What MCP server provides list_gsc_sites? +

list_gsc_sites is provided by the Google Search Console MCP Intel Engine MCP server (surendranb/google-search-console-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Google Search Console MCP Intel Engine tool call.

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

Free to start. No card required.

14 Google Search Console MCP Intel Engine tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.