ClawAudit verdict

clawcall

clawcall-phone

45
🟠 Risky
Significant concerns — only install if you understand the risks

The skill receives phone calls and communicates with a telephony service. While it seems legitimate, the network_in capability could potentially be used for malicious purposes.

⚠ 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.

50
security
70
transparency
90
maintenance

Findings (7)

Pattern match high

HTTP request to bare IP address — common in malicious payloads

references/setup.md · code · http://127.0.0.1

Pattern match medium

References child_process — can spawn system processes

bridge/phone-agent-server.js · prose · downgraded · child_process

Pattern match medium

Uses spawn() — can execute external programs

bridge/phone-agent-server.js · prose · downgraded · spawn(

Pattern match low

Node http/https module — low-level network access

bridge/phone-agent-server.js · prose · downgraded · require("http")

Pattern match low

References agent memory files

bridge/phone-context.js · prose · downgraded · MEMORY.md

Pattern match low

Accesses sensitive environment variables

listener/clawcall-listener.js · prose · downgraded · process.env.CLAWCALL_API_KEY

Pattern match low

References webhook/callback URL

references/setup.md · prose · downgraded · webhook_url

Why the tier is capped

Execution sink present in raw bytes (Hard Floor: class D). Final tier capped at Caution — cannot be lifted by any downgrade, example-payload opt-in, or allowlist.

Permissions & capabilities

Requires 2 environment variables. (1 sensitive: CLAWCALL_API_KEY). Requires 2 system binaries.

network_in

Is this flag fair?

Check another skill Browse the registry Auditing your own skills or configs? Use the API