ClawAudit verdict
agent-deploy
The agent-deploy skill is used to deploy a new isolated OpenClaw agent with its own Telegram bot, workspace, and session storage. Although it executes a script, this action is aligned with its deployment purpose and includes safety measures like validation and auto-rollback.
⚠ 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 (3)
Possible hardcoded credential
scripts/deploy.sh · prose · downgraded · TOKEN="${2:?Usage: deploy.sh <agentId> <botToken> [workspace_path]}
Accesses OpenClaw config/secrets directly
SKILL.md · prose · downgraded · ~/.openclaw/openclaw.json
Python os.environ.get — reads environment variable
scripts/deploy_helper.py · prose · downgraded · os.environ.get(
Why the tier is capped
Execution sink present in raw bytes (Hard Floor: class B). 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.
Is this flag fair?
Thanks — recorded.