search_console_sitemaps_list
List every sitemap registered against a Search Console
This record as markdown: /tools/logly-mureo/search-console-sitemaps-list.md
What search_console_sitemaps_list does on Mureo
AI agents call search_console_sitemaps_list to retrieve information from Mureo without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why search_console_sitemaps_list is rated Low
This tool only reads/queries existing sitemap data from Google Search Console. It has no side effects, does not modify or delete data, and does not execute external operations. The blast radius of misuse is minimal—an AI agent could at most enumerate sitemaps to understand site structure, which is low-risk information already available to site owners or those with Search Console access.
From the tool's definition Tool name contains 'list' and description states 'List every sitemap registered' — a pure retrieval operation with no modification, deletion, or execution of commands.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs search_console_sitemaps_list safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mureo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_console_sitemaps_list, this is the rule to start with:
search_console_sitemaps_list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mureo, apply this rule, and every search_console_sitemaps_list call is checked against it from then on.
Questions about search_console_sitemaps_list
List every sitemap registered against a Search Console. It is categorised as a Read tool in the Mureo MCP Server, which means it retrieves data without modifying state.
Register the Mureo MCP server in PolicyLayer and add a rule for search_console_sitemaps_list: 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 Mureo. Nothing to install.
search_console_sitemaps_list 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 search_console_sitemaps_list 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 search_console_sitemaps_list. 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.
search_console_sitemaps_list is provided by the Mureo MCP server (logly/mureo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mureo, and thousands of servers like it.
This server
Across the catalogue