AI agents call gsc_list_sites to retrieve information from Gsc without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists accessible GSC properties without altering, executing, or deleting any data. It is a pure read operation with minimal blast radius—the worst-case misuse would be unauthorized enumeration of properties an authenticated user already has access to, but no actual harm to data or systems occurs.
From the tool's definition Tool name 'gsc_list_sites' and description 'List every Google Search Console property the authenticated user can access' indicate a query/listing operation with no modification capability. Server description confirms 'read-only tools'.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
List every Google Search Console property the authenticated user can access. It is categorised as a Read tool in the Gsc MCP Server, which means it retrieves data without modifying state.
Register the Gsc MCP server in PolicyLayer and add a rule for gsc_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 Gsc. Nothing to install.
gsc_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 gsc_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 gsc_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.
gsc_list_sites is provided by the Gsc MCP server (jayrockliffe-defused/gsc-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 →