Burrow – Runtime Security for AI Agents
Natural language policies block risky agent actions before they execute.
ongarde-llm content firewall
Transparent proxy blocks agent leaks to LLM APIs without touching agent code.
Operators of self-hosted AI agents (OpenClaw, Agent Zero, CrewAI) in compliance environments
Nightfall DLP · Persona (DLP) · Slack data loss prevention
The filtering list has expanded a bit to include PII, secret keys and I've started a prompt injection library thats being filtered on as well.
The problem: self-hosted agent platforms (OpenClaw, Agent Zero, CrewAI) have no runtime content layer. If your agent leaks an API key, gets prompt injected, or decides to forward someone's SSN to GPT-4, nothing stops it. The platforms don't try to stop it either.
OnGarde is a proxy. You change one line in your config (swap baseUrl) and every request gets scanned before it leaves. Catches credentials, PII, prompt injection, dangerous shell commands. If the scanner fails, it blocks it; never silently passes through.
npx @ongarde/openclaw init handles the OpenClaw setup automatically. Also on PyPI if you're doing something custom.
Dashboard is localhost-only with a SQLite audit log. Nothing phones home.
v1 just shipped: https://github.com/AntimatterEnterprises/ongarde/releases/ta...
I am looking for feedback on this project. Let me hear your thoughts.
Natural language policies block risky agent actions before they execute.
Sandbox agents via natural-language policy, not ambient authority—genuinely novel approach.
Local proxy enforcing markdown rules on LLM output before it hits production.
Self-hosted agent runtime with persistent memory and personality modes via SOUL.md files.
IETF-backed security proxy for MCP agents when the protocol has none.
Eight-layer governance pipeline for agents when LangChain just executes blindly.