searchConsole_delete_site
Remove a site from Google Search Console
This record as markdown: /tools/io-github-alifanov-scopegate/searchconsole-delete-site.md
What searchConsole_delete_site does on ScopeGate
AI agents call searchConsole_delete_site to permanently remove resources in ScopeGate, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why searchConsole_delete_site is rated Critical
This tool irreversibly removes a site from Google Search Console, which could cause loss of all associated search performance data, crawl settings, and verification history for that property. Deletion of a Search Console property is not easily undone and has significant operational impact.
From the tool's definition 'delete_site' and 'Remove a site from Google Search Console'
Attacks that exploit this kind of access
The rule that runs searchConsole_delete_site safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScopeGate, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For searchConsole_delete_site, this is the rule to start with:
searchConsole_delete_site 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 ScopeGate, apply this rule, and every searchConsole_delete_site call is checked against it from then on.
Questions about searchConsole_delete_site
Remove a site from Google Search Console. It is categorised as a Destructive tool in the ScopeGate MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ScopeGate MCP server in PolicyLayer and add a rule for searchConsole_delete_site: 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 ScopeGate. Nothing to install.
searchConsole_delete_site 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 searchConsole_delete_site 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 searchConsole_delete_site. 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.
searchConsole_delete_site is provided by the ScopeGate MCP server (https://mcp.scopegate.cloud/{api_key}). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScopeGate, and thousands of servers like it.
Across the catalogue