polyclaw Security Audit Report

🔭 Continuously monitored by ClawSecure Watchtower

Source:

SHA-256:

polyclaw is an AI agent skill, created by pipethedev and published at openclaw/skills. ClawSecure audited polyclaw across 9 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 80/100 (Safe). The 5 findings concentrate in Command Injection, Permissions Manifest and ReDoS, including Variable $AGENT_ID (line 189) flows to `curl` at line 237. and Variable $AGENT_ID (line 189) flows to `curl` at line 238.. None were rated high or critical severity.

Is polyclaw safe?

ClawSecure audited polyclaw and assigned a security score of 80/100 (Safe), identifying 5 findings across Command Injection and Permissions Manifest. Review the findings below before installing.

What did ClawSecure find in polyclaw?

ClawSecure identified 5 findings in polyclaw, concentrated in Command Injection, Permissions Manifest and ReDoS. The most severe include Variable $AGENT_ID (line 189) flows to `curl` at line 237. and Variable $AGENT_ID (line 189) flows to `curl` at line 238..

How was polyclaw audited?

ClawSecure ran polyclaw through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 9 files from openclaw/skills.

What does a score of 80 mean?

ClawSecure assigned polyclaw a security score of 80/100, placing it in the Safe range. Scores of 80 or above qualify for ClawSecure Verified status; the 5 findings detected are lower-severity. ClawSecure derives this score with a weighted deduction model (critical -20, high -10, medium -5, low -2 from a base of 100).

Audit Findings for polyclaw

ClawSecure detected 5 security findings in polyclaw, spanning Command Injection, Permissions Manifest, ReDoS and Policy Violation.

medium · Variable $AGENT_ID (line 189) flows to `curl` at line 237.. Command Injection finding detected in scripts/register.sh:237.
medium · Variable $AGENT_ID (line 189) flows to `curl` at line 238.. Command Injection finding detected in scripts/register.sh:238.
medium · Missing config.json - agent may not be properly configured. Permissions Manifest finding.
medium · ReDoS vulnerability: Nested quantifiers (potential…. ReDoS finding detected in launch-guide.md:335.
info · Missing License Declaration. Policy Violation finding detected in SKILL.md.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for polyclaw

Harden command execution

polyclaw constructs or runs system commands. Validate that commands are built only from trusted inputs, never pass user-controlled strings directly to a shell, and restrict execution to an allow-list of expected commands.

Add a config.json permissions manifest

A config.json file declares what an agent component can access: file system, network, shell execution and more. Without it, users have no visibility into what the component can do before installing. This is the single most impactful security improvement for any AI agent skill.

Fix ReDoS-prone patterns

polyclaw contains regular expressions vulnerable to catastrophic backtracking (ReDoS). Replace vulnerable patterns, bound input length, and prefer linear-time matching so a crafted input cannot hang the agent.

Resolve policy violations

polyclaw trips ClawSecure policy checks. Review each flagged pattern against your security policy and remediate or document an accepted exception before production use.

Related Security Research

Why Generic Scanners Fail at AI Agent Security→Understanding Our 3-Layer Audit Protocol→How to Secure an MCP Server: The 2026 Guide→

Related AI Agent Security Audits

stock-market-apiScore 95/100 gtsec-smart-stock-selection (1)Score 95/100 gtsec-smart-stock-selectionScore 95/100 gtsec-smart-stock-selectionScore 95/100 skillhubScore 95/100

Scanned on March 18, 2026. polyclaw is one of thousands of agents audited by ClawSecure from the community-curated awesome-openclaw-skills list and the openclaw/skills repository.

Start Your Free Scan