Dawnstar Labs Vardhold Docs

Admin CLI

vardhold.exe is the administrator's command-line tool, for scripts, deployment tools and incident response. It is installed in C:\Program Files\Vardhold.

2 min readUpdated October 2026Vardhold 0.1 (pre-release)

On this page
  1. Commands
  2. status
  3. policy
  4. mode
  5. killswitch
  6. export
  7. verify
  8. version and cleanup-integrations
  9. Connection options
  10. Exit codes
  11. In scripts

Run management commands from an elevated prompt: they read the administrator token, which only Administrators can read. version and policy validate (without --server) work without elevation.

Commands#

status#

PowerShell
vardhold status [--json]

Shows the version, mode, kill switch state, policy version, agents and endpoint capabilities. --json prints the full status object for scripts.

policy#

PowerShell
vardhold policy validate <file> [--base-dir DIR] [--server]
vardhold policy show [--version N]
vardhold policy apply <file>
  • validate checks a policy file and prints each error with its line number. --server asks the running service instead of checking locally; --base-dir sets where list files such as host_not_in are read from.
  • show prints the active policy, or a version from the history.
  • apply validates and applies the file as a new policy version.

mode#

PowerShell
vardhold mode <monitor|enforce|strict>

killswitch#

PowerShell
vardhold killswitch <engage|release|terminate>

engage blocks every checked action, denies pending approvals and suspends agents. terminate ends agent processes instead. release returns to normal.

export#

PowerShell
vardhold export [--format ocsf|cef|json] [--from TIME] [--to TIME] [--agent ID] [--output FILE]

Exports events for a time range and, optionally, one agent. Without --output it writes to the console.

verify#

PowerShell
vardhold verify [--offline] [--db PATH] [--anchor ID:HASH]

Checks the integrity of the audit log: the keyed chain, the sealed approvals, alerts and policy versions, and the record of the chain head.

  • --anchor ID:HASH also checks that the log still holds an event id and hash taken from your SIEM (metadata.sequence and metadata.uid), which catches a rollback or rewrite of the whole log.
  • --offline checks the database directly, without the service; --db points it at a copy.

version and cleanup-integrations#

PowerShell
vardhold version
vardhold cleanup-integrations [--profiles DIR;DIR] [--keep-hook]

cleanup-integrations restores MCP client configurations and removes the hooks. The uninstaller runs it for you; you should not normally need it.

Connection options#

OptionDefault
--url URLThe installed service on 127.0.0.1
--token TOKENThe administrator token in the data folder
--data-dir DIR%ProgramData%\Vardhold

Exit codes#

CodeMeaning
0Success
1Failed, or the input was invalid (for example a policy with errors)
2Usage error
3The service could not be reached
4The integrity check failed

In scripts#

PowerShell
$cli = "C:\Program Files\Vardhold\vardhold.exe"
& $cli verify
switch ($LASTEXITCODE) {
  0 { "Audit log intact" }
  3 { "Vardhold service is not running" }
  4 { Write-Error "Audit log integrity check failed" }
}