ClawAudit verdict
mcp-integration
mcp-adapter
MCP integration guide for discovering and calling tools from configured external MCP servers; the unified list/call interface is consistent with standard MCP usage and no credentials or sensitive data are handled beyond normal tool operation.
⚠ Flagged for review — coarse, uncorroborated signal, not a confirmed exploit. Review the config yourself before installing.
Automated static analysis — not a human review. ClawAudit flags capabilities, not confirmed intent, and can produce false positives. Disagree with this verdict? Use Dispute below.
Findings (6)
Possible hardcoded credential
docs/CONFIGURATION.md · code · API_KEY="your-api-key-here
Accesses OpenClaw config/secrets directly
docs/CONFIGURATION.md · code · ~/.openclaw/openclaw.json
Accesses shell history/config
docs/CONFIGURATION.md · code · ~/.zshrc
References sudo — requests elevated privileges
docs/TROUBLESHOOTING.md · code · sudo
Uses spawn() — can execute external programs
config/openclaw.plugin.json · prose · downgraded · spawn (
Opens WebSocket connection
docs/CHANGELOG.md · prose · downgraded · WebSocket
Why the tier is capped
Execution sink present in raw bytes (Hard Floor: class F). Final tier capped at Caution — cannot be lifted by any downgrade, example-payload opt-in, or allowlist.
Permissions & capabilities
No declared permissions — minimal attack surface.
network_in Is this flag fair?
Thanks — recorded.