List all sites in Google Search Console
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.
This tool queries and returns a list of sites the user has access to in Google Search Console. It retrieves existing data without side effects, making it a Read operation. The severity is low because listing accessible sites poses minimal security risk—it does not expose sensitive performance data, does not modify anything, and simply enumerates resources the authenticated user already has permission to view.
From the tool's definition Tool name 'list_sites' and description 'List all sites in Google Search Console' indicate a retrieval operation with no data modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
List all sites in Google 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.
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.
list_sites is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
list_sites is provided by the Google Search Console MCP Server MCP server (sandriaas/mcp-server-gsc). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →