← Back to Scanner

nodetool Security Audit Report

🔭 Continuously monitored by ClawSecure Watchtower
Source:
SHA-256:

nodetool is an AI agent skill, created by Matthias Georgi <matti.georgi@gmail.com> and published at openclaw/skills. ClawSecure audited nodetool across 3 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 75/100 (Medium Risk). The 5 findings concentrate in Skill Discovery Abuse, Policy Violation and Permissions Manifest, including Potentially dangerous code pattern detected: curl.*\|.*sh and Detects protocol manipulation via capability inflation in skill.... 1 was rated high or critical severity.

Is nodetool safe?

ClawSecure audited nodetool and assigned a security score of 75/100 (Medium Risk), identifying 5 findings across Skill Discovery Abuse and Policy Violation. Review the findings below before installing.

What did ClawSecure find in nodetool?

ClawSecure identified 5 findings in nodetool, concentrated in Skill Discovery Abuse, Policy Violation and Permissions Manifest. 1 was rated high or critical severity. The most severe include Potentially dangerous code pattern detected: curl.*\|.*sh and Detects protocol manipulation via capability inflation in skill....

How was nodetool audited?

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

What does a score of 75 mean?

ClawSecure assigned nodetool a security score of 75/100, placing it in the Medium Risk range. This reflects 5 findings led by Skill Discovery Abuse that warrant review before production use. 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 nodetool

ClawSecure detected 5 security findings in nodetool, spanning Skill Discovery Abuse, Policy Violation, Permissions Manifest and Code Injection.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for nodetool

Resolve policy violations
nodetool trips ClawSecure policy checks. Review each flagged pattern against your security policy and remediate or document an accepted exception before production use.
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.
Eliminate dynamic code execution
nodetool evaluates code at runtime (for example eval or dynamic exec). Remove dynamic evaluation of untrusted input, and where code generation is unavoidable, sandbox it and validate every input.
Pin dependencies to exact versions
Unpinned dependencies allow supply-chain attacks where a compromised version is pulled in automatically. Use exact version numbers in package.json (for example 1.2.3 instead of ^1.2.3) to keep unauthorized code out of your dependency tree. ClawSecure checks every dependency against known CVE databases.

Related Security Research

OWASP ASI Top 10 Explained: The Complete Guide to AI Agent Security Standards→Understanding Our 3-Layer Audit Protocol→How to Secure an MCP Server: The 2026 Guide→

Related AI Agent Security Audits

oh-my-claudecodeScore 80/100opencode-auto-continueScore 90/100shodan-skillScore 90/100clawdhubScore 85/100a2aScore 85/100

Scanned on February 7, 2026. nodetool 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