list_sites

List every Search Console property the authenticated user has access to. Use this first to discover available siteUrl values.

Server Gsc Mcp Connector juju78/gsc-mcp-connector
Category Read
Risk class Low
Parameters 00 required

What list_sites does on Gsc Mcp Connector

AI agents call list_sites to retrieve information from Gsc Mcp Connector without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why list_sites needs a policy

This tool reads and returns metadata about existing Search Console properties accessible to the authenticated user. It has no side effects, does not execute operations, and does not modify any data. While it reveals site access information, the blast radius of accidental misuse is minimal—an agent might list sites it shouldn't see, but this is an information disclosure risk rather than a destructive or financial one.

From the tool's definition Tool explicitly described as 'List every Search Console property' with instruction to use it for 'discover[ing] available siteUrl values' - purely a retrieval operation with no modification or execution.

Risk signalsBulk/mass operation — affects multiple targets

Questions about list_sites

What does the list_sites tool do? +

List every Search Console property the authenticated user has access to. Use this first to discover available siteUrl values. It is categorised as a Read tool in the Gsc Mcp Connector MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_sites? +

Register the Gsc Mcp Connector 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 Gsc Mcp Connector. 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 Gsc Mcp Connector MCP server (juju78/gsc-mcp-connector). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.