Filesystem protection

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

Required protection: This coverage is part of Guard’s required safety floor. Enabling state is always controlled through Guard policy, never from this directory.

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

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.

2 operations · 2 reviewed by default. Examples: rm -r build/ (reviewed by default); chmod -R go-w vendor/ (reviewed by default). These are catalog defaults, not your workspace policy.

This coverage is part of Guard’s required safety floor. Enablement is managed through your workspace's Guard policy and controls — never from this directory. Open the install guidance for the setup flow, then adjust the command coverage for command.filesystem in Guard's policy surface.

The matching action is stopped at Guard's pre-action boundary before it executes, and the decision is recorded with evidence your workspace can review. Exact behavior follows your Guard policy combined with this entry's 2 rules and 2 permission checks.

No. Guard is local-first: interception, decisions, and evidence stay on your machine unless your workspace explicitly configures cloud features. This page is documentation only — it never executes a command or changes protection state.

Guard runs locally alongside the major AI coding agents and MCP-capable harnesses, so this coverage applies wherever Guard intercepts actions. See the supported harness guides at https://hol.org/guard/harnesses for per-tool approval behavior and limitations.

Guard has a free local tier that includes command interception, evidence, and the policy controls this listing documents. Team plans add shared policy, review queues, and audit surfaces. Current plans: https://hol.org/guard/pricing

Open an issue or pull request against the hol-guard repository, where the canonical catalog lives: https://github.com/hashgraph-online/hol-guard Listings are corrected through the same public review process that adds them.

Yes — community coverage is accepted through public pull requests with recorded provenance. Project-maintained listings like this one are extended by the HOL Guard team; propose new operations through the hol-guard repository.

The command mapping table is the audit trail for covered commands and catalog default floors. Pair it with the reviewed rule and permission counts, the per-tool state mapping, and the exact source tree linked from View exact source at the reviewed commit. Guard records enforcement decisions with evidence locally, so what ships matches what you reviewed.