Hi Product Hunt! I’m Mathieu, the maker of GitBlinder. I built it after running several coding agents in a spec-driven workflow and discovering that prompts alone don’t create real boundaries: agents could still inspect unrelated code, overwrite another role’s work, or weaken the tests they were supposed to satisfy. GitBlinder is a local MCP gateway that makes those boundaries enforceable. Each agent connection is bound to a repository, an allowed branch, a tool set, and read/write path rules. Out-of-scope reads simply look absent; out-of-scope writes are rejected atomically. It’s open source, MIT-licensed, and available now on npm as git-blinder@0.1.0. It is early alpha, so I’m especially looking for feedback from teams orchestrating multiple coding agents: which ownership and security boundaries would make this genuinely useful in your workflow?

GitBlinder

Enforce a GitHub perimeter for every coding agent

Enforce a GitHub perimeter for every coding agent