Windows protection
Reviews destructive Windows storage and operating-system commands.
Evidence at a glance
- Source
- Merged native coverage · f440ae1a9f
- Activation
- This coverage is part of Guard’s required safety floor.
- Maintainer
- Project maintained
- Coverage
- 1 rules · 1 permissions
Coverage and limits
Reviews destructive Windows storage and operating-system commands.
- 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 and enforcement
How Guard maps this extension onto your workspace policy: which commands it recognizes, which tools it touches, and how each tool state resolves.
Runtime identity
- Catalog ID
command.windows- Guard enforcement ID
command.windows- Source path
src/codex_plugin_scanner/guard/runtime/command_builtin_extension_registry.py
Tool state mapping
No per-tool overrides are declared. Every tool this extension touches resolves through the workspace Guard policy as-is.
Action classes
windows destructive commandFrequently asked questions
What does Windows protection cover?
Reviews destructive Windows storage and operating-system commands. The listing declares 1 rule and 1 permission check. Coverage is limited to these reviewed operations and the surrounding Guard policy.
Is Windows protection active by default?
Required protection: This coverage is part of Guard’s required safety floor. Enabling state is always controlled through Guard policy, never from this directory.
Who maintains Windows protection?
This listing is maintained by the HOL Guard project itself as part of the native runtime catalog.
Is a listing of Windows protection a security guarantee?
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.