DigitalOcean command protection
Reviews destructive, disruptive, access-changing, credential-exposing and remote-execution doctl operations, while Guard's read proof keeps
Reviews destructive, disruptive, access-changing, credential-exposing and remote-execution doctl operations, while Guard's read proof keeps ordinary doctl list and get reads quiet.
command.cloud.digitalocean · v1.0.0 · Cloud and infrastructure
- Protection rules
- 7
- Permission checks
- 7
- Mapped commands
- 7
Overview
What this coverage does
Reviews destructive, disruptive, access-changing, credential-exposing and remote-execution doctl operations, while Guard's read proof keeps ordinary doctl list and get reads quiet.
Key facts
- Catalog ID
command.cloud.digitalocean- Version
- v1.0.0
- Kind
- Command coverage
- Category
- Cloud and infrastructure
- Protection rules
- 7
- Permission checks
- 7
- Mapped commands
- 7
- Maintainer
- HOL Guard Team(project-maintained)
- Source commit
- d1568ed
- Protection model
- 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.
7 operations · 7 reviewed by default These are catalog defaults, not your workspace policy.
Showing 7 of 7 operations
- Reviewed Guard intercepts the command for review before it runs.Critical
doctl compute droplet delete
DigitalOcean resource deletion
- Default floor
- Reviewed by default. Guard intercepts the command for review before it runs.
- Detector mode
- review
- What it matches
- Identifies deletion of Droplets, volumes, snapshots, images, Kubernetes clusters and node pools, databases, registries, apps, domains, firewalls, load balancers and other DigitalOcean resources through doctl.
- Documented safe variants
Command helpskip this operation when they are the documented preview or help form.- Permission ID
- command.cloud.digitalocean.permission.resource-deletion
- Reviewed Guard intercepts the command for review before it runs.High
doctl compute firewall add-rules
DigitalOcean access change
- Default floor
- Reviewed by default. Guard intercepts the command for review before it runs.
- Detector mode
- review
- What it matches
- Identifies changes to firewall rules, database trusted sources and users, SSH keys, Spaces access keys, project resource assignment, cluster registry access and stored secret values.
- Documented safe variants
Command helpskip this operation when they are the documented preview or help form.- Permission ID
- command.cloud.digitalocean.permission.access-change
- Reviewed Guard intercepts the command for review before it runs.High
doctl auth token
DigitalOcean credential exposure
- Default floor
- Reviewed by default. Guard intercepts the command for review before it runs.
- Detector mode
- review
- What it matches
- Identifies doctl commands that print or store credentials: API tokens, registry Docker credentials, Kubernetes kubeconfig files, database connection strings and user passwords, and partner attachment keys.
- Documented safe variants
Command helpskip this operation when they are the documented preview or help form.- Permission ID
- command.cloud.digitalocean.permission.credential-exposure
- Reviewed Guard intercepts the command for review before it runs.High
doctl registry garbage-collection start
DigitalOcean disruptive operation
- Default floor
- Reviewed by default. Guard intercepts the command for review before it runs.
- Detector mode
- review
- What it matches
- Identifies operations that interrupt or irreversibly change running DigitalOcean resources, such as Droplet power-off, rebuild, restore or resize, registry garbage collection, cluster upgrades, node recycling and database migration.
- Documented safe variants
Command helpskip this operation when they are the documented preview or help form.- Permission ID
- command.cloud.digitalocean.permission.disruptive-operation
- Reviewed Guard intercepts the command for review before it runs.High
doctl apps list --access-token <token>
DigitalOcean inline access token
- Default floor
- Reviewed by default. Guard intercepts the command for review before it runs.
- Detector mode
- review
- What it matches
- Identifies doctl invocations that pass an API access token on the command line with --access-token or -t.
- Permission ID
- command.cloud.digitalocean.permission.inline-access-token
- Reviewed Guard intercepts the command for review before it runs.High
doctl compute ssh
DigitalOcean remote execution
- Default floor
- Reviewed by default. Guard intercepts the command for review before it runs.
- Detector mode
- review
- What it matches
- Identifies doctl commands that open a shell or run code on remote DigitalOcean compute: Droplet SSH, App Platform console, microVM exec and console, and compute plugins.
- Documented safe variants
Command helpskip this operation when they are the documented preview or help form.- Permission ID
- command.cloud.digitalocean.permission.remote-execution
- Reviewed Guard intercepts the command for review before it runs.High
doctl apps list --trace
DigitalOcean request exposure
- Default floor
- Reviewed by default. Guard intercepts the command for review before it runs.
- Detector mode
- review
- What it matches
- Identifies doctl invocations that print full API requests, including the authorization header, with --trace, or that send the account token to another API endpoint with --api-url or -u.
- Permission ID
- command.cloud.digitalocean.permission.request-exposure
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.cloud.digitalocean
- Guard enforcement ID
- command.cloud.digitalocean
- Source path
- contributions/extensions/command.cloud.digitalocean.json
- Contribution digest
sha256…b1f255
Action classes
DigitalOcean access changeDigitalOcean credential exposureDigitalOcean destructive commandDigitalOcean disruptive commandDigitalOcean remote executionTechnical 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 destructive, disruptive, access-changing, credential-exposing and remote-execution doctl operations, while Guard's read proof keeps ordinary doctl list and get reads quiet. The listing declares 7 rules and 7 permission checks. 7 operations · 7 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.
7 operations · 7 reviewed by default. Examples: doctl compute droplet delete (reviewed by default); doctl compute firewall add-rules (reviewed by default); doctl auth token (reviewed by default); doctl registry garbage-collection start (reviewed by default); doctl apps list --access-token <token> (reviewed by default); doctl compute ssh (reviewed by default); doctl apps list --trace (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.cloud.digitalocean 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 7 rules and 7 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.