Google Cloud DNS command protection

Reviews gcloud Cloud DNS managed-zone, record-set, policy, and response-policy deletions and updates.

command.dns.gcp · v1.0.0 · Cloud and infrastructure

By HOL Guard TeamBuilt-in coverageCommand coverage
Install Guard View exact source Documentation About project-maintained coverage

Protection rules

6

Permission checks

6

Mapped commands

21

Overview

What this coverage does

Reviews gcloud Cloud DNS managed-zone, record-set, policy, and response-policy deletions and updates.

Built-in coverage

This coverage is built into the native Guard runtime.

Stated limits

  • Coverage is limited to the reviewed operations and the surrounding Guard policy.
  • A maintainer profile is not a security certification or an official upstream endorsement.

Command mapping

Every command this extension recognizes, with the catalog default floor Guard applies before workspace policy. Search the table, then open an operation for safe variants and the permission ID.

6 operations · 6 reviewed by default These are catalog defaults, not your workspace policy.

Default floor

Showing 6 of 6 operations

  • Reviewed Guard intercepts the command for review before it runs.Critical
    • gcloud dns policies delete
    • gcloud alpha dns policies delete
    • gcloud beta dns policies delete
    Google Cloud DNS policy deletion
    Default floor
    Reviewed by default. Guard intercepts the command for review before it runs.
    Detector mode
    review
    What it matches
    Identifies google cloud dns policy deletion operations.
    Documented safe variants
    --helpskip this operation when they are the documented preview or help form.
    Permission ID
    command.dns.gcp.permission.policy-deletion
  • Reviewed Guard intercepts the command for review before it runs.Critical
    • gcloud dns record-sets delete
    • gcloud alpha dns record-sets delete
    • gcloud beta dns record-sets delete
    Google Cloud DNS record-set deletion
    Default floor
    Reviewed by default. Guard intercepts the command for review before it runs.
    Detector mode
    review
    What it matches
    Identifies google cloud dns record-set deletion operations.
    Documented safe variants
    --helpskip this operation when they are the documented preview or help form.
    Permission ID
    command.dns.gcp.permission.record-deletion
  • Reviewed Guard intercepts the command for review before it runs.Critical
    • gcloud dns record-sets import
    • gcloud alpha dns record-sets import
    • gcloud beta dns record-sets import
    Google Cloud DNS record-set import
    Default floor
    Reviewed by default. Guard intercepts the command for review before it runs.
    Detector mode
    review
    What it matches
    Identifies google cloud dns record-set import operations.
    Documented safe variants
    --helpskip this operation when they are the documented preview or help form.
    Permission ID
    command.dns.gcp.permission.record-import
  • Reviewed Guard intercepts the command for review before it runs.Critical
    • gcloud dns record-sets update
    • gcloud alpha dns record-sets update
    • gcloud beta dns record-sets update
    Google Cloud DNS record-set update
    Default floor
    Reviewed by default. Guard intercepts the command for review before it runs.
    Detector mode
    review
    What it matches
    Identifies google cloud dns record-set update operations.
    Documented safe variants
    --helpskip this operation when they are the documented preview or help form.
    Permission ID
    command.dns.gcp.permission.record-update
  • Reviewed Guard intercepts the command for review before it runs.Critical
    • gcloud dns response-policies delete
    • gcloud alpha dns response-policies delete
    • gcloud beta dns response-policies delete
    • gcloud dns response-policies rules delete
    • gcloud alpha dns response-policies rules delete
    • gcloud beta dns response-policies rules delete
    Google Cloud DNS response-policy deletion
    Default floor
    Reviewed by default. Guard intercepts the command for review before it runs.
    Detector mode
    review
    What it matches
    Identifies google cloud dns response-policy deletion operations.
    Documented safe variants
    --helpskip this operation when they are the documented preview or help form.
    Permission ID
    command.dns.gcp.permission.response-policy-deletion
  • Reviewed Guard intercepts the command for review before it runs.Critical
    • gcloud dns managed-zones delete
    • gcloud alpha dns managed-zones delete
    • gcloud beta dns managed-zones delete
    Google Cloud DNS managed-zone deletion
    Default floor
    Reviewed by default. Guard intercepts the command for review before it runs.
    Detector mode
    review
    What it matches
    Identifies google cloud dns managed-zone deletion operations.
    Documented safe variants
    --helpskip this operation when they are the documented preview or help form.
    Permission ID
    command.dns.gcp.permission.zone-deletion

Tool state mapping

No per-tool overrides are declared. Command defaults above resolve through the workspace Guard policy unless a later policy layer changes them.

Runtime identity

Catalog ID
command.dns.gcp
Guard enforcement ID
command.dns.gcp
Source path
src/codex_plugin_scanner/guard/runtime/command_builtin_extension_registry.py

Action classes

Google DNS destructive command

Technical profile

No independent profile published

This extension has no current independent technical profile. Catalog facts and any legacy launch remain separate and are not presented as profile evidence.

FAQ

Frequently asked questions

Reviews gcloud Cloud DNS managed-zone, record-set, policy, and response-policy deletions and updates. The listing declares 6 rules and 6 permission checks. 6 operations · 6 reviewed by default. Coverage is limited to these reviewed operations and the surrounding Guard policy.

Built-in coverage: This coverage is built into the native Guard runtime. Enabling state is always controlled through Guard policy, never from this directory.

This listing is maintained by the HOL Guard project itself as part of the native runtime catalog.

No. Every listing documents source, activation model, maintainer identity, and stated limitations so you can evaluate coverage before enabling it. Review the stated limitations and the exact source tree before relying on any single control.

6 operations · 6 reviewed by default. Examples: gcloud dns policies delete office (reviewed by default); gcloud dns record-sets delete www --zone public --type A (reviewed by default); gcloud dns record-sets import zone.zone --zone public (reviewed by default); gcloud dns record-sets update www --zone public --type A --rrdatas 192.0.2.1 (reviewed by default); gcloud dns response-policies delete office (reviewed by default); gcloud dns managed-zones delete public (reviewed by default). These are catalog defaults, not your workspace policy.

This coverage is built into the native Guard runtime. Enablement is managed through your workspace's Guard policy and controls — never from this directory. Open the install guidance for the setup flow, then adjust the command coverage for command.dns.gcp in Guard's policy surface.

The matching action is stopped at Guard's pre-action boundary before it executes, and the decision is recorded with evidence your workspace can review. Exact behavior follows your Guard policy combined with this entry's 6 rules and 6 permission checks.

No. Guard is local-first: interception, decisions, and evidence stay on your machine unless your workspace explicitly configures cloud features. This page is documentation only — it never executes a command or changes protection state.

Guard runs locally alongside the major AI coding agents and MCP-capable harnesses, so this coverage applies wherever Guard intercepts actions. See the supported harness guides at https://hol.org/guard/harnesses for per-tool approval behavior and limitations.

Guard has a free local tier that includes command interception, evidence, and the policy controls this listing documents. Team plans add shared policy, review queues, and audit surfaces. Current plans: https://hol.org/guard/pricing

Open an issue or pull request against the hol-guard repository, where the canonical catalog lives: https://github.com/hashgraph-online/hol-guard Listings are corrected through the same public review process that adds them.

Yes — community coverage is accepted through public pull requests with recorded provenance. Project-maintained listings like this one are extended by the HOL Guard team; propose new operations through the hol-guard repository.

The command mapping table is the audit trail for covered commands and catalog default floors. Pair it with the reviewed rule and permission counts, the per-tool state mapping, and the exact source tree linked from View exact source at the reviewed commit. Guard records enforcement decisions with evidence locally, so what ships matches what you reviewed.