Low Risk

list_sites

List all verified sites in Search Console.

How to control list_sites ↓

What list_sites does on Google Search Console MCP Server

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

Low Risk

Why list_sites needs a policy

This tool queries and returns data about verified sites in Search Console without creating, modifying, deleting, or executing any operations. It is a straightforward read operation with minimal risk—it only exposes information the authenticated user already has access to.

From the tool's definition Tool name 'list_sites' and description 'List all verified sites' indicate a retrieval operation with no modifications or side effects.

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

How to control list_sites

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

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

list_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 Server — 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.

Related tools and policies

Go deeper

Questions about list_sites

What does the list_sites tool do? +

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

How do I enforce a policy on list_sites? +

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

What risk level is list_sites? +

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

Can I rate-limit list_sites? +

Yes. Add a rate_limit block to the list_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_sites completely? +

Set action: deny in the PolicyLayer policy for list_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_sites? +

list_sites is provided by the Google Search Console MCP Server MCP server (seotesting-com/gsc-mcp-server). 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 Server tool call.

Start from Google Search Console MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

5 Google Search Console MCP Server tools catalogued and risk-classified — across an index of 43,000+ 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.