List all sites with permission for the GSC Service Account.
AI agents call list_sites to retrieve information from SergeyKrin9/mcp Servers without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about sites associated with a Google Search Console service account. It performs a read-only query operation that returns existing data without creating, modifying, deleting, or executing any actions. The blast radius of misuse is limited to information disclosure about which sites are connected to the account.
From the tool's definition Tool name is 'list_sites' and description states 'List all sites with permission for the GSC Service Account.' The verb 'list' and action of retrieving/querying a set of sites indicates data retrieval with no modifications or side effects.
Attacks that exploit this kind of access
List all sites with permission for the GSC Service Account. It is categorised as a Read tool in the SergeyKrin9/mcp Servers MCP Server, which means it retrieves data without modifying state.
Register the SergeyKrin9/mcp Servers 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 SergeyKrin9/mcp Servers. 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 SergeyKrin9/mcp Servers MCP server (sergeykrin9/mcp-servers). 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 →