Stats
Actions
Tags
From resolve-mcp
Blocks file writes on Edit/Write tool calls using three Python-based guards (env, gitignored, settings drift) and runs pytest after each successful write. Performs file operations via PreToolUse blocking.
2 events · 3 hooks
Safety signals detected in this hook configuration
Where this hook configuration is defined
Defined in hooks/hooks.json
Event handlers and matchers — expand Raw Configuration for the full JSON
Edit|Writeif echo "$CLAUDE_TOOL_INPUT" | grep -qE '\.env"|\.env$'; then echo 'BLOCKED: Do not edit .env files — they contain API keys' >&2; exit 1; fimcp__resolve-mcp__resolve_delete_clips|mcp__resolve-mcp__resolve_delete_timelines|mcp__resolve-mcp__resolve_delete_clips_from_timeline|mcp__resolve-mcp__resolve_reset_grades|mcp__resolve-mcp__resolve_delete_markers|mcp__resolve-mcp__resolve_delete_track|mcp__resolve-mcp__resolve_delete_bins|mcp__resolve-mcp__resolve_delete_stills|mcp__resolve-mcp__resolve_delete_render_job|mcp__resolve-mcp__resolve_delete_all_render_jobs|mcp__resolve-mcp__resolve_delete_projectecho '⚠️ DESTRUCTIVE: This will delete data in DaVinci Resolve that cannot be undone. Confirm with the user before proceeding.' >&2Edit|WriteFILE=$(echo "$CLAUDE_TOOL_INPUT" | grep -oE '"file_path":\s*"[^"]+\.py"' | head -1 | sed 's/.*"\([^"]*\.py\)"/\1/'); if [ -n "$FILE" ] && command -v ruff >/dev/null 2>&1; then ruff format --quiet "$FILE" 2>/dev/null; ruff check --fix --quiet "$FILE" 2>&1 | tail -5; finpx claudepluginhub jenkinsm13/claude-plugins --plugin resolve-mcp