Core safetyCommand contributionv1.0.0Required protection

Filesystem protection

Reviews recursive deletion and access-control changes across filesystem trees.

Claim publisher pageView exact source Documentation

Evidence at a glance

Source
Merged native coverage · f440ae1a9f
Activation
This coverage is part of Guard’s required safety floor.
Maintainer
Project maintained
Coverage
2 rules · 2 permissions

Coverage and limits

Reviews recursive deletion and access-control changes across filesystem trees.

  • 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.

2
Reviewed rules
2
Permission checks
0
Per-tool overrides
v1.0.0
Listing version

Runtime identity

Catalog ID
command.filesystem
Guard enforcement ID
command.filesystem
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

filesystem destructive command

Frequently asked questions

What does Filesystem protection cover?

Reviews recursive deletion and access-control changes across filesystem trees. The listing declares 2 rules and 2 permission checks. Coverage is limited to these reviewed operations and the surrounding Guard policy.

Is Filesystem 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 Filesystem protection?

This listing is maintained by the HOL Guard project itself as part of the native runtime catalog.

Is a listing of Filesystem 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.