Azure DNS command protection
Reviews Azure public DNS, private DNS, virtual-network link, and DNS resolver deletion through Azure CLI.
command.dns.azure · v1.0.0 · Cloud and infrastructure
Protection rules
6
Permission checks
6
Mapped commands
28
Overview
What this coverage does
Reviews Azure public DNS, private DNS, virtual-network link, and DNS resolver deletion through Azure CLI.
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.
Showing 6 of 6 operations
- Reviewed Guard intercepts the command for review before it runs.Critical
az network private-dns link vnet delete
Azure private DNS virtual-network link deletion
- Default floor
- Reviewed by default. Guard intercepts the command for review before it runs.
- Detector mode
- review
- What it matches
- Identifies azure private dns virtual-network link deletion operations.
- Documented safe variants
--helpskip this operation when they are the documented preview or help form.- Permission ID
command.dns.azure.permission.private-link-deletion
- Reviewed Guard intercepts the command for review before it runs.Critical
az network private-dns record-set a deleteaz network private-dns record-set aaaa deleteaz network private-dns record-set cname deleteaz network private-dns record-set mx deleteaz network private-dns record-set ptr deleteaz network private-dns record-set srv deleteaz network private-dns record-set txt delete
Azure private 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 azure private dns record-set deletion operations.
- Documented safe variants
--helpskip this operation when they are the documented preview or help form.- Permission ID
command.dns.azure.permission.private-record-deletion
- Reviewed Guard intercepts the command for review before it runs.Critical
az network private-dns zone delete
Azure private DNS zone deletion
- Default floor
- Reviewed by default. Guard intercepts the command for review before it runs.
- Detector mode
- review
- What it matches
- Identifies azure private dns zone deletion operations.
- Documented safe variants
--helpskip this operation when they are the documented preview or help form.- Permission ID
command.dns.azure.permission.private-zone-deletion
- Reviewed Guard intercepts the command for review before it runs.Critical
az network dns record-set a deleteaz network dns record-set aaaa deleteaz network dns record-set caa deleteaz network dns record-set cname deleteaz network dns record-set ds deleteaz network dns record-set mx deleteaz network dns record-set ns deleteaz network dns record-set ptr deleteaz network dns record-set srv deleteaz network dns record-set tlsa deleteaz network dns record-set txt delete
Azure 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 azure dns record-set deletion operations.
- Documented safe variants
--helpskip this operation when they are the documented preview or help form.- Permission ID
command.dns.azure.permission.public-record-deletion
- Reviewed Guard intercepts the command for review before it runs.Critical
az network dns zone delete
Azure DNS zone deletion
- Default floor
- Reviewed by default. Guard intercepts the command for review before it runs.
- Detector mode
- review
- What it matches
- Identifies azure dns zone deletion operations.
- Documented safe variants
--helpskip this operation when they are the documented preview or help form.- Permission ID
command.dns.azure.permission.public-zone-deletion
- Reviewed Guard intercepts the command for review before it runs.Critical
az dns-resolver deleteaz dns-resolver domain-list deleteaz dns-resolver forwarding-rule deleteaz dns-resolver forwarding-ruleset deleteaz dns-resolver inbound-endpoint deleteaz dns-resolver outbound-endpoint deleteaz dns-resolver vnet-link delete
Azure DNS resolver deletion
- Default floor
- Reviewed by default. Guard intercepts the command for review before it runs.
- Detector mode
- review
- What it matches
- Identifies azure dns resolver deletion operations.
- Documented safe variants
--helpskip this operation when they are the documented preview or help form.- Permission ID
command.dns.azure.permission.resolver-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.azure- Guard enforcement ID
command.dns.azure- Source path
src/codex_plugin_scanner/guard/runtime/command_builtin_extension_registry.py
Action classes
Azure DNS destructive commandTechnical 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 Azure public DNS, private DNS, virtual-network link, and DNS resolver deletion through Azure CLI. 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: az network private-dns link vnet delete -g app -n spoke -z example.test (reviewed by default); az network private-dns record-set a delete -g app -z example.test -n www (reviewed by default); az network private-dns zone delete -g app -n example.test (reviewed by default); az network dns record-set a delete -g app -z example.test -n www (reviewed by default); az network dns zone delete -g app -n example.test (reviewed by default); az dns-resolver delete -g app -n office (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.azure 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.