rawgentic:add-exception

To add security guard exceptions in .rawgentic.json, interactively specify the guard type, rule name, and file path. The system validates these inputs against predefined rulesets and project configurations to unblock legitimate operations safely.

A security guard might flag test files because default rulesets detect suspicious patterns. You can resolve these false positives by adding specific path exclusions to your .rawgentic.json configuration, allowing tests to run without compromising overall security.

Yes, you can exclude specific file paths from WAL guards by configuring per-project exceptions. This requires validating the guard type and rule name against known rulesets to ensure the exclusion does not bypass necessary security guardrails.

The best way to manage guardrail exceptions for blocked operations is through interactive per-project configuration in .rawgentic.json. This approach validates guard types, rule names, and file paths to ensure workflow interruptions are resolved safely and accurately.

Yes, you need to validate rule names when configuring path exclusions. Validation against predefined lists and project configurations ensures that the guard exceptions you add are recognized and applied correctly to unblock legitimate operations.

To unblock legitimate operations blocked by workflow guardrails, add or modify guard rules and path exclusions interactively within your .rawgentic.json file. This process safely manages exceptions while maintaining necessary security validations.