clawsec-config

Audit OpenClaw's openclaw.json for security misconfigurations and remediation advice.

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/4e696b6f/clawsec-agent --skill clawsec-config
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clawsec-config
Source: https://github.com/4e696b6f/clawsec-agent/tree/main/skills/clawsec-config
Command: npx skills add https://github.com/4e696b6f/clawsec-agent --skill clawsec-config

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill identifies critical security misconfigurations within the OpenClaw openclaw.json file, preventing unauthorized access and data exposure.

Core Features & Use Cases

  • Gateway Authentication Check: Verifies if OpenClaw's gateway authentication is enabled.
  • MCP Server Exposure: Detects if internal MCP servers are inadvertently exposed externally.
  • File Permissions Audit: Ensures openclaw.json is not world-readable, protecting sensitive settings.
  • Use Case: A security team can use this Skill to proactively audit their OpenClaw deployments, ensuring that sensitive configuration files are protected and that the gateway is not left open to unauthenticated access.

Quick Start

Run the clawsec-config skill to check the security of your openclaw.json file.

Frequently Asked Questions about clawsec-config

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit openclaw.json for security vulnerabilities?

You can audit openclaw.json for security vulnerabilities by running a configuration audit that checks for disabled gateway authentication, exposed MCP servers, and world-readable file permissions, yielding detailed findings and remediation advice without auto-applying changes.

What security misconfigurations can occur in OpenClaw gateway settings?

Common security misconfigurations in OpenClaw gateway settings include disabled gateway authentication, internal MCP servers inadvertently exposed externally, and world-readable openclaw.json file permissions exposing sensitive configuration data.

How do I check if my MCP servers are exposed externally in OpenClaw?

You can check for externally exposed MCP servers in OpenClaw by auditing the openclaw.json file to detect internal MCP servers inadvertently exposed externally, providing detailed findings and remediation advice to secure the deployment.

Does the OpenClaw configuration audit automatically fix file permission issues?

No, the OpenClaw configuration audit does not auto-apply fixes; it provides detailed findings and remediation advice for world-readable file permissions and other vulnerabilities without applying changes due to the sensitive nature of configuration modifications.

Why does my OpenClaw deployment allow unauthenticated gateway access?

Your OpenClaw deployment allows unauthenticated gateway access because gateway authentication is disabled in the openclaw.json file, a critical vulnerability that a configuration audit can detect and provide specific remediation advice to resolve.