Alternatives
Products that do what FireClaw – Open-source proxy defending AI agents from prompt injection does
Hey HN, We built FireClaw because we kept watching AI agents get owned by prompt injection through web content. The agent fetches a page, the page says "ignore previous instructions," and suddenly your agent is leaking data or running commands it shouldn't. The existing solutions detect injection after the fact. We wanted to prevent it. FireClaw is a security proxy that sits between your AI agent and the web. Every fetch passes through a 4-stage pipeline: 1. DNS blocklist check (URLhaus, PhishTank, community feed) 2. Structural sanitization (strip hidden CSS, zero-width Unicode, encoding…
- 1

Our most accurate Search API for AI agents.
Jul 2026 · docs.firecrawl.dev
- 2

- 3

- 4

- 5PI
People seem to be blindly hooking up their OpenClaw’s to their personal data. So, I built runtime controls to prevent at the least, very simple prompt injection attacks. Once installed, it hooks to Node.js child_process module in the gateway process and listens to tool calls and their response streams. And a fetch hook to monitor user prompts (both could’ve been through fetch, happy to discuss why this whole layer couldn’t just be a proxy). There are two layers of protection: First: Whenever there is a read-only tool call whose response an attacker can modify, we extract that part of the…
Feb 2026 · github.com
- 6

- 7
- 8

- 9

13,000+ MCP servers, skills & plugins for AI coding agents
Jul 2026 · codexmarketplaces.com
- 10

- 11

- 12

- 13

An index for agents pushing the frontier of AI/ML research
Jun 2026 · docs.firecrawl.dev
- 14

- 15

- 16

- 17

- 18OS
Hi HN, Matvey, Ildar, Joey, and Dominik here. If you're building LLM agents that use tools, you're probably worried about prompt injection attacks that can hijack those tools. We were too, and found that solutions like prompt-based filtering or secondary "guard" LLMs can be unreliable. Our thesis is that agent security should be handled at the network level between the agent and the LLM, just like a traditional web application firewall. So we built Archestra Platform: an open-source gateway that acts as a secure proxy for your AI agents. It's designed to be a deterministic firewall against…
Oct 2025 · archestra.ai
- 19

- 20

- 21

- 22PA
We built PrivateClaw because the hosted OpenClaw platforms on the market today require you to trust them with plaintext. PrivateClaw removes that requirement at the hardware layer. PrivateClaw runs AI agents inside Trusted Execution Environments (TEEs), backed by AMD’s SEV-SNP standard. This means that your data is encrypted at the hardware level, enforced by the AMD Secure Processor outside the host OS trust boundary. PrivateClaw comes with inference that also runs inside TEEs, which means your prompts and completions are private as well. How it works: Each user gets a dedicated CVM…
Apr 2026 · privateclaw.dev
- 23

Zero-config hosting to launch specialized AI teams instantly
Feb 2026
- 24MA
Show HN: SEKSBot – AI agents that can't see your secrets SEKSBot is a fork of OpenClaw where agents have zero access to API keys, tokens, or credentials — ever. The core insight is borrowed from SQL prepared statements: separate the instructions from the sensitive data. Agents write requests using named secret references. A broker intercepts and injects the real credentials at execution time. The agent never sees them. How it works: seksh (our nushell fork) has secure built-in commands (seksh-http, seksh-git) that route through the broker. Agents can make authenticated API calls and git…
Feb 2026 · seksbot.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →