List all sites you have access to in Google Search Console. When multiple accounts exist and no account is specified, shows all accounts
AI agents call list_sites to retrieve information from Google Search Console without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries existing data (list of sites/accounts) without creating, modifying, deleting, or executing any operations. It is a simple read/list operation with minimal security impact.
From the tool's definition Tool name 'list_sites' and description 'List all sites you have access to in Google Search Console' indicate a retrieval operation with no side effects. The phrase 'shows all accounts' confirms read-only listing behavior.
Attacks that exploit this kind of access
List all sites you have access to in Google Search Console. When multiple accounts exist and no account is specified, shows all accounts. It is categorised as a Read tool in the Google Search Console MCP Server, which means it retrieves data without modifying state.
Register the Google Search Console 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. 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 (lionkiii/google-searchconsole-mcp). 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 →