Gate risky coding-agent tool calls

01 · Role in the system

What Jev does here

Before bash, write, or edit calls, Jev scores destructive impact, exfiltration, and scope risk. After selected command results, it checks for leaked credentials and classifies failures so code can append fixed advice. Shadow mode is the default, all error paths fail open, and enforcement requires explicit configuration.

02 · Control boundary

Where Jev sits

Tool intent and bounded output to parallel risk judgments; extension code applies thresholds and user-confirmation policy.

Code owns the loop, permissions, thresholds, validation, and side effects. Jev owns only the bounded judgments described above.

03 · Known limits

What this evidence does not prove

• The smoke calibration is small and does not establish reliable safety performance.
• Failures fail open, and tool arguments or output excerpts are sent to the TypeSafe API.

04 · Attribution

Public sources

This is a Community record: the project was published by a third-party community author.

• y0usaf ↗Community · github · public · checked 2026-09-18