🛡️ OpenClaw Guardrail Linter

The problem

Misconfigured OpenClaw agents risk remote code execution, secret leakage, and unrestricted tool access. Standard linters miss these platform-specific security flaws in openclaw.json and workspace manifests.

What it does

• Scans config files for OGL001-OGL011 security violations.
• Identifies hardcoded secrets and insecure environment variable mapping.
• Detects sandbox escapes and dangerous Docker bind mounts.
• Flags bypasses where write permissions are denied but edit tools remain active.
• Evaluates inbound DM permissions and broad skill gates.

Frameworks & tools

Compatible with OpenClaw configuration formats including .json and .json5. Analyzes SOUL.md, AGENTS.md, and USER.md files.

Why this beats prompting it yourself

Manual prompting often misses nuanced bypasses like OGL005 or specific Docker sandbox overrides. This skill uses a codified rule set that ensures consistent detection of 11 distinct vulnerability classes without hallucinatory false negatives.

Use cases

• Reviewing openclaw.json before deploying a new agent gateway.
• Auditing local workspace mounts for unnecessary read-write access.
• Checking AGENTS.md for hardcoded API keys or sensitive literal strings.
• Pre-production security checks for OpenClaw skill gates.

Known limitations

Uses heuristic analysis of static text files. It does not verify live gateway state or network-level firewall rules.