Google Cloud Storage command protection
Reviews Google CLI storage commands including copy, list, sync, and deletion.
command.storage.google-cloud · v1.0.0 · Data and resilience
- Protection rules
- 7
- Permission checks
- 7
- Mapped commands
- 7
Overview
What this coverage does
Reviews Google CLI storage commands including copy, list, sync, and deletion.
Key facts
- Catalog ID
command.storage.google-cloud- Version
- v1.0.0
- Kind
- Command coverage
- Category
- Data and resilience
- Protection rules
- 7
- Permission checks
- 7
- Mapped commands
- 7
- Maintainer
- HOL Guard Team(project-maintained)
- Source commit
- 00d0807
- 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.
Use cases
Reviewed workflows that reference this coverage
Browse all use casesCommand 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 · 5 reviewed by default · 2 allowed 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
gcloud storage rm
Google Cloud Storage deletion
- Default floor
- Reviewed by default. Guard intercepts the command for review before it runs.
- Detector mode
- review
- What it matches
- Identifies google cloud storage deletion operations.
- Documented safe variants
Google Cloud Storage deletion helpGoogle storage sync dry rungsutil sync no-actskip this operation when they are the documented preview or help form.- Permission ID
- command.storage.google-cloud.permission.deletion
- Reviewed Guard intercepts the command for review before it runs.High
gcloud storage buckets create
Google Cloud Storage bucket create
- Default floor
- Reviewed by default. Guard intercepts the command for review before it runs.
- Detector mode
- review
- What it matches
- Identifies google cloud storage bucket create operations.
- Documented safe variants
Google Cloud Storage bucket create helpskip this operation when they are the documented preview or help form.- Permission ID
- command.storage.google-cloud.permission.buckets-create
- Reviewed Guard intercepts the command for review before it runs.High
gcloud storage cp
Google Cloud Storage copy
- Default floor
- Reviewed by default. Guard intercepts the command for review before it runs.
- Detector mode
- review
- What it matches
- Identifies google cloud storage copy operations.
- Documented safe variants
Google Cloud Storage copy helpskip this operation when they are the documented preview or help form.- Permission ID
- command.storage.google-cloud.permission.cp
- Reviewed Guard intercepts the command for review before it runs.High
gcloud storage mv
Google Cloud Storage move
- Default floor
- Reviewed by default. Guard intercepts the command for review before it runs.
- Detector mode
- review
- What it matches
- Identifies google cloud storage move operations.
- Documented safe variants
Google Cloud Storage move helpskip this operation when they are the documented preview or help form.- Permission ID
- command.storage.google-cloud.permission.mv
- Reviewed Guard intercepts the command for review before it runs.High
gcloud storage rsync
Google Cloud Storage sync
- Default floor
- Reviewed by default. Guard intercepts the command for review before it runs.
- Detector mode
- review
- What it matches
- Identifies google cloud storage sync operations.
- Documented safe variants
Google Cloud Storage sync helpskip this operation when they are the documented preview or help form.- Permission ID
- command.storage.google-cloud.permission.rsync
- Allowed Guard recognizes the command and does not intercept it unless workspace policy tightens it.Low
gcloud storage cat
Google Cloud Storage cat
- Default floor
- Allowed by default. Guard recognizes the command and does not intercept it unless workspace policy tightens it.
- Detector mode
- disabled
- What it matches
- Identifies google cloud storage cat operations.
- Documented safe variants
Google Cloud Storage cat helpskip this operation when they are the documented preview or help form.- Permission ID
- command.storage.google-cloud.permission.cat
- Allowed Guard recognizes the command and does not intercept it unless workspace policy tightens it.Low
gcloud storage ls
Google Cloud Storage list
- Default floor
- Allowed by default. Guard recognizes the command and does not intercept it unless workspace policy tightens it.
- Detector mode
- disabled
- What it matches
- Identifies google cloud storage list operations.
- Documented safe variants
Google Cloud Storage list helpskip this operation when they are the documented preview or help form.- Permission ID
- command.storage.google-cloud.permission.ls
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.storage.google-cloud
- Guard enforcement ID
- command.storage.google-cloud
- Source path
- contributions/extensions/command.storage.google-cloud.json
- Contribution digest
sha256…c35a12
Action classes
Google storage 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 Google CLI storage commands including copy, list, sync, and deletion. The listing declares 7 rules and 7 permission checks. 7 operations · 5 reviewed by default · 2 allowed 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 · 5 reviewed by default · 2 allowed by default. Examples: gcloud storage rm (reviewed by default); gcloud storage buckets create (reviewed by default); gcloud storage cp (reviewed by default); gcloud storage mv (reviewed by default); gcloud storage rsync (reviewed by default); gcloud storage cat (allowed by default); gcloud storage ls (allowed 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.storage.google-cloud 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.