DataMan command protection
Reviews state-mutating DataMan CLI commands that initialize projects, scaffold tables or databases, generate/apply migrations, modify creden
Reviews state-mutating DataMan CLI commands that initialize projects, scaffold tables or databases, generate/apply migrations, modify credentials, or export sensitive audit and telemetry logs.
command.dataman · v1.0.0 · Other extensions
- Protection rules
- 10
- Permission checks
- 8
- Mapped commands
- 6
Overview
What this coverage does
Reviews state-mutating DataMan CLI commands that initialize projects, scaffold tables or databases, generate/apply migrations, modify credentials, or export sensitive audit and telemetry logs.
Key facts
- Catalog ID
command.dataman- Version
- v1.0.0
- Kind
- Command coverage
- Category
- Other extensions
- Protection rules
- 10
- Permission checks
- 8
- Mapped commands
- 6
- Maintainer
- Community contributor(community, provenance recorded)
- Source commit
- c296abe
- Protection model
- External · opt-in
External coverage. It must be enabled through Guard controls; this page does not activate it.
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.
10 operations · 10 reviewed by default These are catalog defaults, not your workspace policy.
Showing 10 of 10 operations
- Reviewed Guard intercepts the command for review before it runs.HighMatcher metadata only
DataMan change-password
- Default floor
- Reviewed by default. Guard intercepts the command for review before it runs.
- Detector mode
- review
- What it matches
- Reviews dataman users change-password invocations.
- Permission ID
- command.dataman.permission.user-admin
- Reviewed Guard intercepts the command for review before it runs.HighMatcher metadata only
DataMan create-admin
- Default floor
- Reviewed by default. Guard intercepts the command for review before it runs.
- Detector mode
- review
- What it matches
- Reviews dataman users create-admin invocations.
- Permission ID
- command.dataman.permission.user-admin
- Reviewed Guard intercepts the command for review before it runs.High
dataman users create-token ServiceAccount --scopes "customer:read"
DataMan create-token
- Default floor
- Reviewed by default. Guard intercepts the command for review before it runs.
- Detector mode
- review
- What it matches
- Reviews dataman users create-token invocations that provision access tokens.
- Permission ID
- command.dataman.permission.create-token
- Reviewed Guard intercepts the command for review before it runs.High
dataman migrate
DataMan migrate
- Default floor
- Reviewed by default. Guard intercepts the command for review before it runs.
- Detector mode
- review
- What it matches
- Reviews dataman migrate invocations that modify database schema and data.
- Permission ID
- command.dataman.permission.migrate
- Reviewed Guard intercepts the command for review before it runs.Medium
dataman create database analytics
DataMan create database
- Default floor
- Reviewed by default. Guard intercepts the command for review before it runs.
- Detector mode
- review
- What it matches
- Reviews dataman create database invocations that provision database directories.
- Permission ID
- command.dataman.permission.create-database
- Reviewed Guard intercepts the command for review before it runs.Medium
dataman create table Employee -o crud
DataMan create table
- Default floor
- Reviewed by default. Guard intercepts the command for review before it runs.
- Detector mode
- review
- What it matches
- Reviews dataman create table invocations that scaffold schema tables.
- Permission ID
- command.dataman.permission.create-table
- Reviewed Guard intercepts the command for review before it runs.MediumMatcher metadata only
DataMan export-audit
- Default floor
- Reviewed by default. Guard intercepts the command for review before it runs.
- Detector mode
- review
- What it matches
- Reviews dataman logs export-audit invocations.
- Permission ID
- command.dataman.permission.export-logs
- Reviewed Guard intercepts the command for review before it runs.MediumMatcher metadata only
DataMan export-telemetry
- Default floor
- Reviewed by default. Guard intercepts the command for review before it runs.
- Detector mode
- review
- What it matches
- Reviews dataman logs export-telemetry invocations.
- Permission ID
- command.dataman.permission.export-logs
- Reviewed Guard intercepts the command for review before it runs.Medium
dataman init
DataMan init
- Default floor
- Reviewed by default. Guard intercepts the command for review before it runs.
- Detector mode
- review
- What it matches
- Reviews dataman init invocations.
- Permission ID
- command.dataman.permission.init
- Reviewed Guard intercepts the command for review before it runs.Medium
dataman makemigration
DataMan makemigration
- Default floor
- Reviewed by default. Guard intercepts the command for review before it runs.
- Detector mode
- review
- What it matches
- Reviews dataman makemigration invocations that write migration files.
- Permission ID
- command.dataman.permission.makemigration
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.dataman
- Guard enforcement ID
- command.dataman
- Source path
- contributions/extensions/command.dataman.json
- Contribution digest
sha256…dc17bc
Action classes
DataMan project initialization commandDataMan database table scaffolding commandDataMan database namespace creation commandDataMan schema migration generation commandDataMan database migration execution commandDataMan administrative user management commandDataMan programmatic API token creation commandDataMan audit and telemetry log export 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 state-mutating DataMan CLI commands that initialize projects, scaffold tables or databases, generate/apply migrations, modify credentials, or export sensitive audit and telemetry logs. The listing declares 10 rules and 8 permission checks. 10 operations · 10 reviewed by default. Coverage is limited to these reviewed operations and the surrounding Guard policy.
External · opt-in: External coverage. It must be enabled through Guard controls; this page does not activate it. Enabling state is always controlled through Guard policy, never from this directory.
This listing entered the catalog as a community contribution through a public pull request with recorded provenance, with public credit to @vikashgraja, and 1 GitHub maintainer is recorded on the listing. Credit is attribution only. A verified publisher profile and the claim flow verify authority separately; neither is an upstream endorsement or a HOL safety certification.
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.
10 operations · 10 reviewed by default. Examples: DataMan change-password (reviewed by default); DataMan create-admin (reviewed by default); dataman users create-token ServiceAccount --scopes "customer:read" (reviewed by default); dataman migrate (reviewed by default); dataman create database analytics (reviewed by default); dataman create table Employee -o crud (reviewed by default); DataMan export-audit (reviewed by default); DataMan export-telemetry (reviewed by default). The remaining 2 operations are listed in the command mapping table. These are catalog defaults, not your workspace policy.
External coverage. It must be enabled through Guard controls; this page does not activate it. 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.dataman 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 10 rules and 8 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 extensions are merged through public pull requests with recorded provenance, and you can claim the publisher page for a contribution you maintain through the Publisher Studio.
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.