{"author":"talbuilds","children":[{"author":"talbuilds","children":[],"created_at":"2025-08-29T21:55:33.000Z","created_at_i":1756504533,"id":45069882,"options":[],"parent_id":45068582,"points":null,"story_id":45068582,"text":"A couple of extra notes I didn\u2019t fit in the main post:<p>\u2013 The firewall runs entirely client-side, so no data ever leaves your environment.<p>\u2013 It focuses on *retrieval-time* risks, not output moderation \u2014 so the LLM never sees poisoned chunks in the first place.<p>\u2013 Policies are YAML: you can choose to deny, allow, or just re-rank risky docs (based on recency, provenance, relevance).<p>\u2013 Overhead is low: scanners are regex&#x2F;heuristic, so for ~5\u201320 chunks it adds only a few ms.<p>I\u2019d love feedback on two things in particular:<p>1. Do you think retrieval-time filtering belongs in the pipeline, or should it all be done at ingest&#x2F;output?<p>2. If you\u2019ve got prompt injection payloads or edge cases you use to test your own RAG stacks, I\u2019d love to try them against this.<p>Thanks for taking a look \u2014 always happy to hear critique, especially from folks running LangChain&#x2F;LlamaIndex in production.","title":null,"type":"comment","url":null},{"author":"talbuilds","children":[],"created_at":"2025-08-30T15:07:00.000Z","created_at_i":1756566420,"id":45075303,"options":[],"parent_id":45068582,"points":null,"story_id":45068582,"text":"300+ installs in 24h, RAG Firewall now with GraphRAG support.","title":null,"type":"comment","url":null},{"author":"danshalev7","children":[],"created_at":"2025-09-01T07:02:44.000Z","created_at_i":1756710164,"id":45090229,"options":[],"parent_id":45068582,"points":null,"story_id":45068582,"text":"Very interesting","title":null,"type":"comment","url":null}],"created_at":"2025-08-29T19:48:12.000Z","created_at_i":1756496892,"id":45068582,"options":[],"parent_id":null,"points":1,"story_id":45068582,"text":"RAG pipelines are great, but they can still retrieve &quot;toxic&quot; chunks:\n\u2013 prompt injection attempts\n\u2013 leaked API keys&#x2F;secrets\n\u2013 stale or conflicting content\n\u2013 unapproved external URLs<p>We built an open-source &quot;retrieval firewall&quot; that scans chunks <i>before</i> they reach the LLM:\n\u2013 denies injection &amp; secrets\n\u2013 flags&#x2F;reranks PII, encoded blobs, untrusted URLs\n\u2013 audit log (JSONL) of all decisions\n\u2013 drop-in wrappers for LangChain and LlamaIndex retrievers<p>Install: pip install rag-firewall\nRepo: <a href=\"https:&#x2F;&#x2F;github.com&#x2F;taladari&#x2F;rag-firewall\" rel=\"nofollow\">https:&#x2F;&#x2F;github.com&#x2F;taladari&#x2F;rag-firewall</a><p>Curious if others here handle retrieval-time risks, or just ingest&#x2F;output filtering.\nWould love feedback and red-team payloads.","title":"Show HN: RAG Firewall \u2013 retrieval-time guardrails for LangChain/LlamaIndex","type":"story","url":"https://github.com/taladari/rag-firewall"}
