Get details for a specific sitemap.
AI agents call get_sitemap_tool to retrieve information from MCP Google Search Console without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata and information about a sitemap without creating, modifying, deleting, or executing operations. It is a straightforward read operation that queries existing sitemap properties. The blast radius of misuse is minimal—an attacker could only view sitemap details they already have access to through the Search Console account.
From the tool's definition Tool name 'get_sitemap_tool' and description 'Get details for a specific sitemap' indicate a retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
Get details for a specific sitemap. It is categorised as a Read tool in the MCP Google Search Console MCP Server, which means it retrieves data without modifying state.
Register the MCP Google Search Console MCP server in PolicyLayer and add a rule for get_sitemap_tool: 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 MCP Google Search Console. Nothing to install.
get_sitemap_tool 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 get_sitemap_tool 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 get_sitemap_tool. 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.
get_sitemap_tool is provided by the MCP Google Search Console MCP server (crunchtools/mcp-google-search-console). 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 →