careful

To prevent destructive shell commands like rm -rf from executing, you need a guardrail that inspects input via a PreToolUse Bash hook. This mechanism blocks unapproved actions during interactive sessions, requiring explicit user confirmation or an override before proceeding.

Yes, you can add a warning prompt for git push --force and git reset --hard in production environments. Safety guardrails monitor these specific patterns, issuing warnings and blocking execution until you confirm the decision to proceed or cancel.

A PreToolUse hook works by intercepting and analyzing bash command input before execution. It logs usage events locally, detects destructive patterns, and returns a programmatic decision to either proceed after a warning or cancel the operation entirely.

Yes, safety guardrails support an override mechanism to proceed after a warning. They are designed to be safe for shared and production environments by offering exceptions for known safe targets while still logging usage events locally.

In shared environments, you should monitor for destructive operations such as rm -rf, git push --force, git reset --hard, kubectl delete, and similar dangerous shell commands. Implementing a warning system prevents catastrophic edits to deployments and databases.