nodetool
georgi/nodetool⭐ 0🔧 0 tools
D5.2SpiderScore (registry)
⚠ Hard constraint applied: critical issue caps D
Decision
Allow with Risk
Confidence
90%
nodetool has risks — usable with isolation (5.23/10, 1 critical, 1 high).
Recommended Actions
- highRun In Container1 critical vulnerabilities require isolation
- highLimit PermissionsRestrict tool access to minimum required scope
Do Not
- ✗running in production without container isolation
Risk Flags (2)
- criticalnodetool×2[TS-E002] Remote script downloaded and executed directly
- highsandbox.not_configured[TS-C009] No sandbox
How This Was Decided
- positivew=0.5Overall quality score = 5.23/10 (grade D)
- negativew=0.81 critical security issue(s) detected
- negativew=0.51 high-severity issue(s) detected
- positivew=0.3Tool description clarity score = 5.78/10
Source: SpiderRating automated security scanUpdated: 2026-03-13Protocol: v1.1
Description Quality
Composite: 5.8 / 10
3-Layer Breakdown
Description (38%)
5.8
Security (34%)
5.0
Metadata (28%)
4.4
Description Dimensions
Intent Clarity
4.5
Permission Scope
6.5
Side Effects
3.5
Capability Disclosure
6.0
Operational Boundaries
9.0
Security Analysis
5.0
Score
1
Critical
1
High
0
Medium
0
Low
Findings Redacted
Detailed security findings are hidden during the 90-day responsible disclosure window. Maintainers have been notified.
1 HIGH2 CRITICAL
Metadata Health
Provenance (40%)
6.5
Maintenance (35%)
1.5
Popularity (25%)
5.1
Badge
Add this badge to your README:
[](https://spiderrating.com/servers/georgi/nodetool)🛡️
Protect Your Agents
Get a free API key. Every MCP tool call checked against 15,923 rated servers in real-time.
Get Free API Key →📊
Monitor All Your Servers
Dashboard for your entire MCP portfolio. Score tracking, alerts, and compliance reports.
Start Free Trial →⭐
Scan Locally (Open Source)
Run SpiderShield on your own machine. 46+ security rules, zero data leaves your system.
Star on GitHub →