searchConsole_list_sitemaps

List sitemaps submitted for a site

SERVERScopeGate SOURCEhttps://mcp.scopegate.cloud/{api_key}

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-alifanov-scopegate/searchconsole-list-sitemaps.md

WHAT IT DOES

What searchConsole_list_sitemaps does on ScopeGate

AI agents call searchConsole_list_sitemaps to retrieve information from ScopeGate without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why searchConsole_list_sitemaps is rated Low

This tool retrieves and displays existing sitemap submissions without creating, modifying, deleting, or executing any operations. It is a read-only retrieval of metadata about Google Search Console sitemaps, posing minimal risk even if misused by an agent.

From the tool's definition Tool name contains 'list' and description states 'List sitemaps submitted for a site' — a query operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs searchConsole_list_sitemaps safely

PolicyLayer is an MCP gateway: it sits between your AI agents and ScopeGate, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For searchConsole_list_sitemaps, this is the rule to start with:

searchConsole_list_sitemaps Allowed

searchConsole_list_sitemaps is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "searchConsole_list_sitemaps": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect ScopeGate, apply this rule, and every searchConsole_list_sitemaps call is checked against it from then on.

FAQ

Questions about searchConsole_list_sitemaps

What does the searchConsole_list_sitemaps tool do? +

List sitemaps submitted for a site. It is categorised as a Read tool in the ScopeGate MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on searchConsole_list_sitemaps? +

Register the ScopeGate MCP server in PolicyLayer and add a rule for searchConsole_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 ScopeGate. Nothing to install.

What risk level is searchConsole_list_sitemaps? +

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

Can I rate-limit searchConsole_list_sitemaps? +

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

Set action: deny in the PolicyLayer policy for searchConsole_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 searchConsole_list_sitemaps? +

searchConsole_list_sitemaps is provided by the ScopeGate MCP server (https://mcp.scopegate.cloud/{api_key}). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on ScopeGate, and thousands of servers like it.

This server

All 385 ScopeGate tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →