Ripple blocks commits when AI agents edit outside approved scope
u/bluetech333 built an open-source tool called Ripple that uses a git commit hook and MCP server to block commits when an AI coding agent modifies files outside a pre-approved task boundary.
Score breakdown
Ripple introduces an automated, local enforcement layer between AI agent edits and the git history, replacing the manual process of scanning large diffs for unapproved changes with a structured commit-time boundary check.
- 01u/bluetech333 built an open-source tool called Ripple to catch AI coding agents that edit files outside a pre-approved task boundary.
- 02Ripple uses an MCP server to save the approved scope before the AI runs.
- 03A local git commit hook checks staged files against the saved boundary and blocks the commit if out-of-scope changes are detected.
u/bluetech333 on r/cursor describes a common pain point with AI coding agents: when given a narrow task, agents sometimes make additional changes outside the specified boundary under the guise of being "helpful." Manually hunting for those unapproved edits in a large `git diff` is error-prone, since `git diff` shows what changed but not what was authorized to change.
To solve this, they built and open-sourced Ripple, published as `@getripple/cli` on npm.
To solve this, they built and open-sourced Ripple, published as `@getripple/cli` on npm. The tool works in two steps: before the AI runs, an MCP server saves the approved task boundary as a checkpoint; after the AI finishes, a local git commit hook inspects the staged files and compares them against that saved boundary. If any file or function was touched outside the approved scope, the commit is blocked. Rather than a generic error, Ripple outputs a "Review Packet" in the terminal that lists the original approved scope alongside every out-of-bounds change the AI made.
Ripple deliberately does not auto-delete the extra code, on the grounds that some AI-initiated changes outside the original scope may be genuinely necessary. Instead, it pauses the workflow so a human can review the packet and decide whether to revert the extra files or explicitly expand the approved scope. The tool runs entirely locally with no cloud uploads or accounts required.
Key facts
- 01u/bluetech333 built an open-source tool called Ripple to catch AI coding agents that edit files outside a pre-approved task boundary.
- 02Ripple uses an MCP server to save the approved scope before the AI runs.
- 03A local git commit hook checks staged files against the saved boundary and blocks the commit if out-of-scope changes are detected.
- 04When a violation is found, Ripple outputs a 'Review Packet' in the terminal showing the original approved scope and every out-of-bounds file or function touched.
- 05Ripple does not auto-delete unapproved changes — it pauses the workflow for human review.
- 06The tool runs 100% locally with no cloud uploads or accounts.
- 07It was published as V1 on npm under the package name `@getripple/cli`.
Topics
Summary and scoring are generated automatically from the original article. We always link back to the publisher and never republish images or paywalled content. Last processed Jun 15, 2026 · 11:57 UTC. How this works →