Delete a sitemap from Google Search Console.
AI agents call delete_sitemap to permanently remove resources in Google Search Console MCP Intel Engine — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a sitemap from Google Search Console is an irreversible action that removes configuration data and can degrade search engine visibility and indexing. This cannot be undone through normal tool operations and represents data loss, placing it in the Destructive category with high severity due to potential negative impact on site visibility and SEO performance.
From the tool's definition Tool name is 'delete_sitemap' and description states 'Delete a sitemap from Google Search Console.' The verb 'delete' explicitly indicates irreversible removal of data.
Documented attack patterns abuse exactly the kind of access delete_sitemap gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Google Search Console MCP Intel Engine, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_sitemap:
{
"version": "1",
"default": "deny",
"hide": [
"delete_sitemap"
]
}delete_sitemap disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a sitemap from Google Search Console. It is categorised as a Destructive tool in the Google Search Console MCP Intel Engine MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Google Search Console MCP Intel Engine MCP server in PolicyLayer and add a rule for delete_sitemap: 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 Google Search Console MCP Intel Engine. Nothing to install.
delete_sitemap 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 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. 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 is provided by the Google Search Console MCP Intel Engine MCP server (surendranb/google-search-console-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 14 Google Search Console MCP Intel Engine tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
14 Google Search Console MCP Intel Engine tools catalogued and risk-classified — across an index of 42,500+ MCP servers.