Remove a sitemap from Search Console.
AI agents call delete_sitemap_tool to permanently remove resources in MCP Google Search Console — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a sitemap from Search Console removes indexing guidance and cannot be undone without re-submitting. This is a destructive action that permanently alters the website's search engine configuration. While not directly damaging content, it causes irreversible loss of Search Console configuration state, justifying 'Destructive' over 'Write'.
From the tool's definition Tool name includes 'delete' and description states 'Remove a sitemap from Search Console' — this irreversibly deletes configuration data.
Attacks that exploit this kind of access
Remove a sitemap from Search Console. It is categorised as a Destructive tool in the MCP Google Search Console MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Google Search Console MCP server in PolicyLayer and add a rule for delete_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.
delete_sitemap_tool is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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 delete_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.
delete_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 →