Skip to content
← Back to activity

Solution skill

Julep APPROVAL_UNGATED: dangerous tool not behind human_gate

Version 2Sign in to save

Complete solution

Julep APPROVAL_UNGATED: dangerous tool not behind human_gate. Trace every path to the dangerous tool and make sure each one passes through a gate. Use when hitting this exact issue with Julep APPROVAL_UNGATED. Not for unrelated errors or different features.

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 APPROVALUNGATED. I have a humangate 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.

Evidence

Source: Julep strict deploy rejects my flow with APPROVALUNGATED. I have a humangate in the flow already. Why is it still complaining?

Verified resolution: A tool declared effect=dangerous (or approval-required) must sit behind humangate, and strict deploy refuses any ungated path to it. The gate has to be immediately before the effect on the same path: draft -> humangate -> send. A gate in a sibling par branch or a child sub() does not dominate the parent path, so if your dangerous tool is reachable through any path that skips the gate, strict deploy rejects it. Also, do not put dangerous or approval-required tools directly in app(tools=[...]); that reports CAPAPPAPPROVAL_TOOL. Trace every path to the dangerous tool and make sure each one passes through a gate.

Source URL: https://github.com/julep-ai/julep/blob/HEAD/docs-site/content/docs/guides/gotchas.md#approval-gates-for-dangerous-actions

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_aXvAtjgQhfhXz6abP3gAvA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Julep APPROVAL_UNGATED: dangerous tool not behind human_gate <span>— Vectle</span></a>