This is exactly the scenario that destructive-guard hooks are designed to prevent. A PreToolUse hook can block file operations targeting paths outside the project directory:

#!/bin/bash
# scope-guard.sh — block file operations outside project directory
INPUT=$(cat)
TOOL=$(echo "$INPUT" | jq -r '.tool_name // empty' 2>/dev/null)
CMD=$(echo "$INPUT" | jq -r '.tool_input.command // empty' 2>/dev/null)
[[ "$TOOL" != "Bash" || -z "$CMD" ]] && exit 0

# Skip echo/printf (string output, not actual deletion)
echo "$CMD" | grep -qE '^\s*(echo|printf|cat\s*<<)' && exit 0

# Block destructive commands targeting paths outside current project
if echo "$CMD" | grep -qE '\brm\b.*(-[a-zA-Z]*r|-[a-zA-Z]*f|--recursive|--force)'; then
    TARGETS=$(echo "$CMD" | grep -oP 'rm\s+(-[a-zA-Z]+\s+)*\K.*')
    for target in $TARGETS; do
        case "$target" in
            /*)  echo "BLOCKED: absolute path: $target" >&2; exit 2 ;;
            ~/*)  echo "BLOCKED: home directory: $target" >&2; exit 2 ;;
            ../*)  echo "BLOCKED: parent escape: $target" >&2; exit 2 ;;
        esac
    done
fi

# Block targeting system/user directories
if echo "$CMD" | grep -qiE '(rm|del).*(Desktop|Applications|Documents|Downloads|Library|Keychain)'; then
    echo "BLOCKED: targeting system/user directory" >&2
    exit 2
fi
exit 0

Settings:

{
  "hooks": {
    "PreToolUse": [{
      "matcher": "Bash",
      "hooks": [{ "type": "command", "command": "~/.claude/hooks/scope-guard.sh" }]
    }]
  }
}

This blocks any recursive/force deletion that targets absolute paths, home directory paths, or parent directory escapes. It also specifically blocks deletion of macOS system directories like Desktop, Applications, Library, and Keychain.

For a comprehensive setup, npx cc-safe-setup installs 8 safety hooks including a destructive-guard that catches dangerous patterns automatically.

Issue closed - please delete #36233

Description

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions