Back to browse
GitHub Repository

Security firewall for agents

689 starsGo

Claw Patrol, a security firewall for agents

by rough-sea·Jun 9, 2026·92 points·26 comments

AI Analysis

●●●BangerBig BrainZero to OneSolve My Problem

Wire-protocol parsing gates agent actions before they hit production—no LLM gateway does this.

Strengths
  • Wire-level protocol parsing extracts facts for CEL expressions without relying on API-level controls
  • HCL rules block destructive SQL and pause kubectl deletes until human approval
  • WireGuard and Tailscale tunneling with per-process netns tunneling on Linux and macOS
Weaknesses
  • Go-based proxy adds deployment complexity to existing agent workflows
  • Protocol parsing coverage may not include all edge cases for every supported service
Category
Target Audience

DevOps engineers, platform teams running AI agents

Similar To

Tailscale · OpenPolicyAgent · HashiCorp Boundary

Post Description

At Deno we've been using OpenClaw and other agents increasingly for addressing production problems in Deno Deploy - when a PagerDuty alert fires, the agent starts researching the cause and making fixes.

In order to do this, the agent needs access to real production systems - postgres, kubernetes, gcp, clickhouse, github, etc. But this is dangerous to say the least - we want destructive actions to be reviewed by other LLMs, approved by humans, and logged appropriately.

Claw Patrol terminates TCP connections over WireGuard or Tailscale, then parses application protocols (eg http, postgres, ssh) to apply rules that allow you to deny/allow requests.

There are a few projects that sit as a proxy in front of agents to do secret injection or apply various guardrails, but none met our needs (LLM gateways, MCP proxies, sandboxes), particularly the need to handle low-level protocols, or handle complex real world situations like tunneling postgres through k8s.

Written in Go, configured in HCL, MIT licensed. Happy to answer any questions.

Similar Projects