Missing fail-closed enforcement
HighAV-EXEC-004Execution authorizationCore pack
What it finds
Absence of an explicit `failClosed`/deny-by-default pattern, or a throw tied to a verification/authorization failure.
Why it matters
Without a hard block on verification failure, a failed check is only a warning — execution proceeds anyway.
How to fix it
Ensure every verification failure explicitly blocks execution (deny by default).
Pro shows the corrected code for your exact file, step by step, and re-scans to confirm the fix. See plans
Check details
- Finding code
- MISSING_FAIL_CLOSED
- How it detects
- Flags a safety control that should be there but is not.
- Confidence
- Likely: strong signal, but review it in context.
- Scans
- Any text-based agent config or source
Check your agent for this
Paste your agent code or MCP config. The free scan runs all 124 checks in about 10 seconds — no account needed.