gcp_dns_delete_managed_zone

Delete a managed zone

SERVERGCP MCP Server SOURCEahmedselimmansor-ctrl/gcp_mcp_server
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ahmedselimmansor-ctrl-gcp-mcp-server/gcp-dns-delete-managed-zone.md

What gcp_dns_delete_managed_zone does on GCP MCP Server

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

Why gcp_dns_delete_managed_zone is rated Critical

This tool irreversibly removes a DNS managed zone, causing immediate and complete loss of DNS service for any domains managed by that zone. Recovery requires manual recreation and reconfiguration. This is a classic Destructive action that cannot be undone automatically. Severity is high because DNS outage impacts availability of services, though it does not move money or expose data directly.

From the tool's definition Tool name contains 'delete' and description states 'Delete a managed zone' — a DNS managed zone is a critical infrastructure resource whose deletion is irreversible and will break all DNS resolution for associated domains.

Questions about gcp_dns_delete_managed_zone

What does the gcp_dns_delete_managed_zone tool do? +

Delete a managed zone. It is categorised as a Destructive tool in the GCP MCP Server 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 gcp_dns_delete_managed_zone? +

Register the GCP MCP Server MCP server in PolicyLayer and add a rule for gcp_dns_delete_managed_zone: 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 GCP MCP Server. Nothing to install.

What risk level is gcp_dns_delete_managed_zone? +

gcp_dns_delete_managed_zone 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 gcp_dns_delete_managed_zone? +

Yes. Add a rate_limit block to the gcp_dns_delete_managed_zone 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 gcp_dns_delete_managed_zone completely? +

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

gcp_dns_delete_managed_zone is provided by the GCP MCP Server MCP server (ahmedselimmansor-ctrl/gcp_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on GCP MCP Server, 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 GCP MCP Server'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.