New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

delete_search_console_site

Remove a property from the connected Google account. THIS LOSES HISTORY: the account loses access to that property\

SERVERHermoso SOURCEhttps://app.hermoso.ai/mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/hermoso/delete-search-console-site.md

What delete_search_console_site does on Hermoso

AI agents call delete_search_console_site to permanently remove resources in Hermoso, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_search_console_site is rated Critical

An AI agent that decides to call delete_search_console_site doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Hermoso is gone. There is no undo for destructive operations.

Questions about delete_search_console_site

What does the delete_search_console_site tool do? +

Remove a property from the connected Google account. THIS LOSES HISTORY: the account loses access to that property\. It is categorised as a Destructive tool in the Hermoso MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_search_console_site? +

Register the Hermoso MCP server in PolicyLayer and add a rule for delete_search_console_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 Hermoso. Nothing to install.

What risk level is delete_search_console_site? +

delete_search_console_site is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_search_console_site? +

Yes. Add a rate_limit block to the delete_search_console_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.

How do I block delete_search_console_site completely? +

Set action: deny in the PolicyLayer policy for delete_search_console_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.

What MCP server provides delete_search_console_site? +

delete_search_console_site is provided by the Hermoso MCP server (https://app.hermoso.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Hermoso, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Hermoso's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.