Operator-only Vault KV runtime injection into a trusted local process.

version
0.1.0
GitHub stars
436

Install

/plugin install vault-kv@grc-engineering-suite

Run it inside Claude Code after adding the marketplace with /plugin marketplace add GRCEngClub/claude-grc-engineering.

Contents

Discovered from source

Skills 1

Vault KV expert

Direct operators to /vault-kv:run. Never invoke the runtime helper on their behalf, request or display secret values, or include secrets in evidence. Explain that this increment supports one KV field in a trusted child process, not dynamic secrets, automatic evidence collection, or Vault authentication setup. Distinguish mocked tests from live verification and point to the linked official Vault docs.

Commands 1

/vault-kv:run

Do not run this helper from an agent, ask for secret values, or capture provider or child output. An authorized operator can run it in a trusted terminal after configuring VAULT_ADDR, TLS verification, and authenticating the Vault CLI using the organization's approved method. Install a trusted Vault CLI on PATH. The CLI supports token-based authentication and previously authenticated AppRole sessions; this helper does not perform login or accept credentials in arguments.

node /path/to/vault-kv/scripts/run.js 2 secret evidence/service api_key -- /path/to/trusted-command

Specify the actual mount version (1 or 2); do not guess. The helper uses it to select the KV v1 or KV v2 JSON data shape, not to verify the mount version. This invokes vault kv get -format=json -mount=secret evidence/service and injects the selected field only as VAULT_KV_VALUE into the child. The entire secret at that path is retrieved into helper memory, not just the selected field. Mount and secret path are separate. The selected field must be a nonempty UTF-8 string without NUL; no trimming or newline is added. Unsupported values and provider errors fail closed. Provider and child output are suppressed, stdin is closed, and no shell is used. Provider calls time out after 15 seconds; the trusted command has no timeout. Exit 0 means the child succeeded, 1 means provider/payload/child failure, and 2 means invalid usage. Errors are generic.

Grant the identity read only on the selected data path, e.g. secret/evidence/service for KV v1 or secret/data/evidence/service for KV v2. CLI mount discovery may need access depending on deployment; consult Vault's policy guidance rather than granting broad privileges. Secret paths and field names are arguments and may appear in process listings and Vault audit logs; do not put secret values in them. Vault audit configuration governs what is recorded server-side.

Only use a trusted command: it can persist, transmit or log the value even though its stdout and stderr are suppressed. VAULT_TOKEN is removed from the child environment, but other inherited environment variables and Vault CLI token-helper files may still allow access. Local privileged processes may inspect memory or environments. The helper cannot erase all in-memory copies. Never place secrets in evidence, chat, shell history, or command arguments; the operator must secure the host and any child-generated files. Restrict access to those artifacts.

This is a manual runtime helper, not automatic integration with evidence collection or IaC scans. It does not generate dynamic credentials, write to Vault, manage leases, authenticate AppRole, or emit findings. Those remain future scope; do not assume a read operation always has no side effects for non-KV engines.

Sources: Vault KV get, KV v1 API, KV v2 API, Vault policies, Vault CLI. Offline tests use a mock vault executable; no live Vault compatibility or account permissions have been verified.

Sponsors

Details

Marketplace
GRCEngClub/claude-grc-engineering
Source
plugins/connectors/vault-kv
Category
Community

More from GRCEngClub/claude-grc-engineering

All 70