1. The Problem: AI coding agents read your files and run commands on user's or developer's machine. One prompt injection, one careless request, and the .env, SSH keys, AWS credentials, or customer PII gets sent to the model — and potentially logged, cached, or leaked. OpenClaw's native read and exec tools have no security gate. Anything the agent asks for, it gets. 2. The Purpose of Security Plugin: It provides custom security layer for OpenClaw's native read and exec tools with DLP-gated versions that scan every request before it executes: - Layer 1 — Path/filename check: Blocks .env, .ssh/, .aws/credentials, .pem, .npmrc, and 60+ sensitive file patterns instantly - Layer 2 — Content scan: Scans file contents for SSNs, credit cards, API keys, JWTs, medical record numbers, HIPAA identifiers, and 15+ PII patterns — even in PDFs, Excel, Word, and CSV files - Layer 3 — Command validation: Blocks printenv, cat ~/.env, curl -d @secrets, nc, ssh-keygen -y, and 16 exfiltration/credential-dump patterns - Global exec hook: Intercepts ALL command execution — plugins, workflows, and agents can't bypass it 3. What Makes It Different: - Zero config. Install, restart gateway, done. No rules to write, no YAML to edit - Binary distribution. The DLP engine is compiled — no source code shipped, no programming language dependencies, no supply chain risk - Content-aware. Doesn't just check filenames — scans what's inside. A file called notes.txt containing SSN: 123-45-6789 gets blocked - Two layers of defense. Even if the LLM is prompt-injected into wanting to read your secrets, the tool-level block stops it before execution 4. Why We Built It We built Securityplugin v1 to address the critical need for enhanced security and privacy within the OpenClaw environment. As OpenClaw operates with access to sensitive system files, commands, and data, a dedicated security plugin is essential to prevent unauthorized access, data leaks, and harmful actions. Securityplugin v1 acts as a proactive safeguard that enforces strict controls, protects sensitive credentials, and mitigates risks from potentially malicious or accidental operations. Our goal was to create a reliable, configurable, and transparent security layer that empowers users to confidently use OpenClaw without compromising their system's integrity or privacy. 5. How it works: User: "Read ~/.env" → OpenClaw routes to secure_read (plugin) → Plugin spawns DLP binary → Layer 1: filename blocked (.env) → DENIED. Content never leaves your machine.

SecureMind

Blocks security leaks & data exposure in OpenClaw agents

Blocks security leaks & data exposure in OpenClaw agents