Routine vs. High-Impact Actions
Learn how Noxgild treats ordinary work differently from destructive or security-sensitive operations.
Noxgild classifies capabilities so routine work can stay efficient while higher-impact actions receive stronger controls.
Routine actions
Examples include reading files, listing directories, inspecting process state, and taking browser snapshots. These actions still require valid account, computer, scope, schema, worker, and policy checks.
Higher-impact actions
Destructive operations such as deleting files or terminating processes can require exact per-command approval before dispatch.
A request that crosses from untrusted browser content into Machine or Desktop control can also require exact approval even when the underlying action would normally be routine.
Human verification
CAPTCHA, OTP/2FA, passkeys, secure-desktop prompts, and similar challenges are human actions rather than approvable commands.