Add Omega Walls to Tools and code#130
Open
anviren wants to merge 1 commit intoPuliczek:mainfrom
Open
Conversation
Adds Omega Walls to the “Tools and code” section. Omega Walls is an open-source stateful prompt-injection defense layer for RAG and agent pipelines, including MCP-connected workflows. It is designed as a runtime trust boundary across untrusted content, memory, context, and tools, with focus on distributed / cross-step attacks, secret-exfiltration pressure, and unsafe tool activation. I placed it in “Tools and code” because it fits alongside MCP security wrappers, gateways, and monitoring tools.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds Omega Walls to the “Tools and code” section.
Omega Walls is an open-source stateful prompt-injection defense layer for RAG and agent pipelines, including MCP-connected workflows. It is designed as a runtime trust boundary across untrusted content, memory, context, and tools, with focus on distributed / cross-step attacks, secret-exfiltration pressure, and unsafe tool activation.
I placed it in “Tools and code” because it fits alongside MCP security wrappers, gateways, and monitoring tools.