uivoid command protection
Reviews uivoid commands that create or reconfigure a live MCP server mapped from an existing API, rotate the credential it calls that API wi
Reviews uivoid commands that create or reconfigure a live MCP server mapped from an existing API, rotate the credential it calls that API with, or write local session and skill files a later command or agent session will trust.
command.uivoid · v1.0.0 · Other extensions
- Protection rules
- 5
- Permission checks
- 5
- Mapped commands
- 5
Overview
What this coverage does
Reviews uivoid commands that create or reconfigure a live MCP server mapped from an existing API, rotate the credential it calls that API with, or write local session and skill files a later command or agent session will trust.
Key facts
- Catalog ID
command.uivoid- Version
- v1.0.0
- Kind
- Command coverage
- Category
- Other extensions
- Protection rules
- 5
- Permission checks
- 5
- Mapped commands
- 5
- Maintainer
- Community contributor(community, provenance recorded)
- Source commit
- 2adc5c1
- 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.
5 operations · 5 reviewed by default These are catalog defaults, not your workspace policy.
Showing 5 of 5 operations
- Reviewed Guard intercepts the command for review before it runs.High
uivoid create my-app
uivoid live project creation
- Default floor
- Reviewed by default. Guard intercepts the command for review before it runs.
- Detector mode
- review
- What it matches
- Identifies `uivoid create`, which creates a live project on the user's uivoid account and, unless run with `--no-discover`, generates an outbound credential and maps one or more real API operations as callable MCP tools before activating the endpoint. There is no dry-run mode: every invocation performs a real write, and destructive (DELETE-mapped) operations can be exposed non-interactively with…
- Documented safe variants
uivoid create command help (--help)uivoid create command help (-h)skip this operation when they are the documented preview or help form.- Permission ID
- command.uivoid.permission.create
- Reviewed Guard intercepts the command for review before it runs.High
uivoid credentials my-app
uivoid outbound credential rotation
- Default floor
- Reviewed by default. Guard intercepts the command for review before it runs.
- Detector mode
- review
- What it matches
- Identifies `uivoid credentials <project>`, which rotates the live outbound secret an already-deployed uivoid project uses to authenticate against the target API.
- Documented safe variants
uivoid credentials command help (--help)uivoid credentials command help (-h)skip this operation when they are the documented preview or help form.- Permission ID
- command.uivoid.permission.credentials
- Reviewed Guard intercepts the command for review before it runs.High
uivoid oauth-config my-app
uivoid OAuth passthrough configuration
- Default floor
- Reviewed by default. Guard intercepts the command for review before it runs.
- Detector mode
- review
- What it matches
- Identifies `uivoid oauth-config <project>`, which switches a project's authentication mode to OAuth/JWT passthrough and writes the identity provider's issuer, JWKS endpoint, audience, and client credentials.
- Documented safe variants
uivoid oauth-config command help (--help)uivoid oauth-config command help (-h)skip this operation when they are the documented preview or help form.- Permission ID
- command.uivoid.permission.oauth-config
- Reviewed Guard intercepts the command for review before it runs.Medium
uivoid login
uivoid session credential write
- Default floor
- Reviewed by default. Guard intercepts the command for review before it runs.
- Detector mode
- review
- What it matches
- Identifies `uivoid login`, which writes a bearer session (personal access token, account email, and organization) to `~/.config/uivoid/config.json`. Every later uivoid command trusts this file until `uivoid logout` clears it.
- Documented safe variants
uivoid login command help (--help)uivoid login command help (-h)skip this operation when they are the documented preview or help form.- Permission ID
- command.uivoid.permission.login
- Reviewed Guard intercepts the command for review before it runs.Low
uivoid skill --install
uivoid agent skill install
- Default floor
- Reviewed by default. Guard intercepts the command for review before it runs.
- Detector mode
- review
- What it matches
- Identifies `uivoid skill --install`, which copies a bundled skill file to `~/.codex/skills/uivoid/SKILL.md` that a Codex agent will load automatically in later sessions. Bare `uivoid skill` (no `--install`) only prints the file's local path and is never reviewed.
- Documented safe variants
uivoid skill-install command help (--help)uivoid skill-install command help (-h)skip this operation when they are the documented preview or help form.- Permission ID
- command.uivoid.permission.skill-install
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.uivoid
- Guard enforcement ID
- command.uivoid
- Source path
- contributions/extensions/command.uivoid.json
- Contribution digest
sha256…b172a1
Action classes
uivoid live project creation commanduivoid outbound credential rotation commanduivoid oauth passthrough configuration commanduivoid session credential write commanduivoid agent skill install 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 uivoid commands that create or reconfigure a live MCP server mapped from an existing API, rotate the credential it calls that API with, or write local session and skill files a later command or agent session will trust. The listing declares 5 rules and 5 permission checks. 5 operations · 5 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. 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.
5 operations · 5 reviewed by default. Examples: uivoid create my-app (reviewed by default); uivoid credentials my-app (reviewed by default); uivoid oauth-config my-app (reviewed by default); uivoid login (reviewed by default); uivoid skill --install (reviewed by default). 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.uivoid 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 5 rules and 5 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.