ClawHub
Back to skill

Security audit

SidClaw Governance

Security checks for vulnerabilities and agentic risk

Overview

This governance skill appears purpose-aligned, but it routes configured tool calls through a third-party proxy that can control and audit them, with privacy and secret-handling details underexplained.

Install only if you intend SidClaw to be a trusted third-party governance and audit provider for the MCP servers you route through it. Before use, review SidClaw's data handling and retention terms, limit proxying to intended tools, protect and rotate the API key, prefer pinned package versions where possible, and keep a rollback copy of your OpenClaw configuration.

SkillSpector

Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (2)

Missing User Warnings

Medium
Confidence
92% confidence
Finding
The README states that every MCP tool call is evaluated by SidClaw and logged with an audit trail, which strongly implies tool-call metadata and possibly sensitive arguments are transmitted to an external service. Without an explicit privacy warning, data-flow description, and guidance on what leaves the host, users may unknowingly route confidential prompts, credentials, queries, or file contents to a third party.

Missing User Warnings

Low
Confidence
95% confidence
Finding
The README instructs users to place API keys directly in ~/.openclaw/openclaw.json, a persistent local configuration file, but does not warn about file permissions, accidental commits, backups, or other local disclosure paths. Storing long-lived secrets in plaintext configuration materially increases the chance of credential leakage and subsequent unauthorized access to the SidClaw account or governance controls.

Static analysis

No suspicious patterns detected.