---
title: "Comment by Mayank Bansal on \"Stop Committing Secrets: Automatically Generate .env.example with gen-envex\" | Hashnode"
description: "This is exactly the kind of thing runtime guardrails are for. I'm making Failproof AI, use policies to block access to sensitive files like .env before the agen"
url: "https://hashnode.com/posts/stop-committing-secrets-automatically-generate-env-example-with-gen-envex/6a57cd832a25ace6dd6c4bfa/comment/6a585802635bba76b8fbd2ed"
---

[Discussion](https://hashnode.com/posts/stop-committing-secrets-automatically-generate-env-example-with-gen-envex/6a57cd832a25ace6dd6c4bfa)

Comment [Stop Committing Secrets: Automatically Generate .env.example with gen-envex](https://hashnode.com/posts/stop-committing-secrets-automatically-generate-env-example-with-gen-envex/6a57cd832a25ace6dd6c4bfa)

[Mayank Bansal](https://hashnode.com/@monk1)

[Jul 16](https://hashnode.com/posts/stop-committing-secrets-automatically-generate-env-example-with-gen-envex/6a57cd832a25ace6dd6c4bfa/comment/6a585802635bba76b8fbd2ed)

This is exactly the kind of thing runtime guardrails are for. I'm making Failproof AI, use policies to block access to sensitive files like .env before the agent ever gets to execute the read. It's completely open source just check out the repo of Failproof AI. Hit the star also if helpful :)
