google-search-console.delete_sitemap
Remove a sitemap URL from Search Console for a verified property. Call google-search-console.list_sites to discover sites, then google-search-console.list_sitemaps for an exact feed_path. Omit site_url to use the default property. This only removes the sitemap from Search Console tracking; it doe...
This record as markdown: /tools/io-github-vee3io-vee3/google-search-console.delete-sitemap.md
What google-search-console.delete_sitemap does on Vee3
AI agents call google-search-console.delete_sitemap to permanently remove resources in Vee3, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
site_url | object | — | Optional property URL from google-search-console.list_sites. When omitted, the default property is used. The user or agent passes an exact site_url value from t |
feed_path | string | Yes | Full sitemap URL for the property, for example https://example.com/sitemap.xml. Use an exact path from google-search-console.list_sitemaps when available. |
Parameters from the server's own tool schema.
Why google-search-console.delete_sitemap is rated Critical
Irreversibly removes sitemap tracking from Search Console; cannot be easily undone.
From the tool's definition Remove a sitemap URL from Search Console
Attacks that exploit this kind of access
The rule that runs google-search-console.delete_sitemap safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Vee3, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For google-search-console.delete_sitemap, this is the rule to start with:
google-search-console.delete_sitemap is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Vee3, apply this rule, and every google-search-console.delete_sitemap call is checked against it from then on.
Questions about google-search-console.delete_sitemap
Remove a sitemap URL from Search Console for a verified property. Call google-search-console.list_sites to discover sites, then google-search-console.list_sitemaps for an exact feed_path. Omit site_url to use the default property. This only removes the sitemap from Search Console tracking; it does not delete the sitemap file from the website. Cost = 10 tokens. It is categorised as a Destructive tool in the Vee3 MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
google-search-console.delete_sitemap accepts 2 parameters: site_url, feed_path. Required: feed_path. The full parameter table on this page comes from the server's own tool schema.
Register the Vee3 MCP server in PolicyLayer and add a rule for google-search-console.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 Vee3. Nothing to install.
google-search-console.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 google-search-console.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 google-search-console.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.
google-search-console.delete_sitemap is provided by the Vee3 MCP server (https://mcp.vee3.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Vee3, and thousands of servers like it.
Across the catalogue