@membrane-ai/membrane-guard-gateway
v0.0.3
Published
OpenClaw plugin that validates agent inputs, tool calls, and messages through the Membrane AI guard API
Maintainers
Readme
Membrane AI Guard Gateway
An OpenClaw plugin that protects your AI agents from harmful prompts, secret leakage, and unauthorized tool execution.
Membrane acts as a security layer between your users and your AI agents. Every incoming message and tool call is validated in real-time through the Membrane API, which returns an allow/block/warn decision before the agent can act.
Why use Membrane?
- Prompt injection protection — Block malicious inputs before they reach your agent
- Tool call authorization — Prevent agents from executing dangerous or unauthorized tools
- Secret leakage prevention — Stop sensitive data from being exposed through agent responses
- Risk-based decisions — Each validation returns a risk level, category, and reason so you stay informed
- Zero-config security — Install, add your API key, and your agents are protected
Installation
openclaw plugins install @membrane-ai/membrane-guard-gatewayQuick Start
1. Register for an API Key:
https://membraneai-client-production.up.railway.app/
2. Set your API key:
Use the built-in slash command from any connected channel:
/membrane api-key set <YOUR_API_KEY>Your key is stored locally at ~/.membrane/config.json and never leaves your machine (except as a Bearer token to the Membrane API).
3. That's it. Membrane is now validating all messages and tool calls for your agents.
How It Works
Membrane hooks into every stage of the OpenClaw agent lifecycle:
| What's protected | How | |---|---| | Incoming messages | Validated against the Membrane API before the agent sees them | | Tool calls | Checked before execution — blocked calls never run | | Outbound messages | Monitored for policy compliance |
Each validation returns a structured response:
decision: "allow" | "block" | "warn"
risk_level: "low" | "medium" | "high"
category: "prompt_injection" | "secret_leakage" | ...
reason: "Human-readable explanation"When a tool call is blocked, the agent receives a clear reason and the tool is never executed.
Policy Types
Configure the validation policy that matches your agent's use case:
| Policy | Description |
|---|---|
| readonly_agent | Agents that only read data — strictest tool restrictions |
| public_agent | Customer-facing agents — balanced input/output validation |
| internal_ops | Internal automation — relaxed but monitored |
| research_agent | Research/exploration agents — permissive with logging |
Commands
| Command | Description |
|---|---|
| /membrane api-key set <KEY> | Save your Membrane API key |
| /membrane summary | View your plan, usage, and remaining quota |
Requirements
- Node.js 18+
- OpenClaw installed and configured
- A Membrane API key
License
MIT
