list_sitemaps

List every sitemap submitted for a Search Console property, with last submission and processing status.

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

What list_sitemaps does on Gsc Mcp Connector

AI agents call list_sitemaps 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_sitemaps needs a policy

This tool retrieves information about sitemaps that have been submitted to a Google Search Console property. It has no side effects, does not modify data, and does not execute external operations. The blast radius of misuse is minimal—an attacker could enumerate sitemaps to map site structure, but this information is typically accessible to anyone with GSC property access and poses no direct harm.

From the tool's definition Tool description states it 'List[s] every sitemap' with metadata about submission and status. No modification, deletion, or execution capability—purely retrieves and queries existing sitemap records.

Risk signalsBulk/mass operation — affects multiple targets

Questions about list_sitemaps

What does the list_sitemaps tool do? +

List every sitemap submitted for a Search Console property, with last submission and processing status. 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_sitemaps? +

Register the Gsc Mcp Connector MCP server in PolicyLayer and add a rule for list_sitemaps: 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_sitemaps? +

list_sitemaps is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_sitemaps? +

Yes. Add a rate_limit block to the list_sitemaps 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_sitemaps completely? +

Set action: deny in the PolicyLayer policy for list_sitemaps. 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_sitemaps? +

list_sitemaps 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.