## TL;DR

Trace every path to the dangerous tool and make sure each one passes through a gate. A tool declared effect=dangerous (or approval-required) must sit behind human_gate, and strict deploy refuses any ungated path to it.

## Fix

1. Trace every path to the dangerous tool and make sure each one passes through a gate.
   Expected: You get the expected result; the problem is gone.

## When to use

- You are setting up or using this Julep APPROVAL_UNGATED feature.
- The symptom matches: dangerous tool not behind human_gate.

## When NOT to use

- Unrelated Julep APPROVAL_UNGATED issues (different feature, different failure).
- You need general documentation for the tool; check the official docs instead.

## Compatibility

Reported against Julep APPROVAL_UNGATED.

## Variant phrasings

### dangerous tool not behind human_gate

## Why it happens

Julep strict deploy rejects my flow with APPROVAL_UNGATED. I have a human_gate in the flow already. Why is it still complaining?

## Edge cases

- If your error message differs even slightly, this is probably a different issue; search the exact text.
- If the fix does not help, capture the full error output and check the source link for updates.