PRIVATE BETA · FOR SELF-HOSTED OPENCLAW
Your agent has root.Contain it.
A proxy in front of OpenClaw that checks every message, tool call and skill before your agent acts.
Autonomy is the attack surface.
Three published OpenClaw CVEs. The gateway hardener checks for each.
Read more
OpenClaw gets your terminal, filesystem and API keys. That access is what makes it useful, and it is what an attacker inherits when one layer fails. Scores are from the public CVE records.
Unauthenticated access
Admin endpoints trust 127.0.0.1. Behind a bad proxy, that's everyone.
1-click RCE
An unvalidated gatewayUrl leaks the auth token to a remote WebSocket.
Docker sandbox escape
PATH manipulation lets a sandboxed skill run commands on the host.
230 malicious ClawHub skills reported in one week. The #1-ranked one sent the user's .env to an attacker.
Eight checks. No code changes.
WhatsApp · Telegram · skills
ClawShield · 8 checks
OpenClaw gateway :18789
Point your channels at the proxy with one env var. Every decision streams to the console.
- 01
Credential Vault
Keys are swapped for tokens at the proxy. The model never sees them.
- 02
Prompt Firewall
Strips hijack instructions from WhatsApp, Telegram and skill output.
- 03
Skill Scanner
Checks ClawHub packages before install, statically and by behaviour.
- 04
Gateway Hardener
Pins WebSocket origins. Drops the localhost-is-trusted assumption.
- 05
Command Gatekeeper
Shell and file calls need a policy match. PATH tricks get denied.
- 06
DLP Engine
Scans outbound tool calls for secrets and PII before they leave.
- 07
Memory Defense
Integrity-checks long-term memory so a poisoned note can't stick.
- 08
Runtime Monitor
Flags burst tool calls, new egress hosts and privilege jumps.
8
Checks per request
40,000+
Exposed instances reported
230
Bad skills in one week
0
Code changes needed
Put a perimeter around your agent.
One email when the beta opens. Nothing else.