Discord Tool Status

Security checks across malware telemetry and agentic risk

Overview

This plugin does what it claims: it posts live OpenClaw tool-call status to Discord, with a privacy caveat around debug logging and visible tool parameters.

Install only if you are comfortable with the bot posting tool-call names, parameters, and statuses into the relevant Discord conversation. Avoid using it in channels where tool arguments may contain secrets or sensitive user data, and keep verbose/debug plugin logs restricted or disabled until the context logging is minimized.

SkillSpector

By NVIDIA

Vulnerability Patterns

Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (2)

Context-Inappropriate Capability

Low

Confidence: 89% confidence
Finding: The helper logs the entire hook context via JSON.stringify(ctx), which can expose sessionKey, accountId, channel identifiers, conversation identifiers, and other metadata to application logs. In a messaging/Discord-integrated skill, these logs may be accessible to operators, shared log systems, or third-party observability tooling, creating unnecessary disclosure of sensitive operational data.

Missing User Warnings

Medium

Confidence: 83% confidence
Finding: The code emits sensitive context data to logs without minimization or evidence of user disclosure/consent. Because this hook processes Discord-related session state, the context is more sensitive than generic telemetry: it can reveal account linkage, session ownership, and message-routing metadata that could aid correlation or misuse if logs are exposed.

VirusTotal

61/61 vendors flagged this plugin as clean.

View on VirusTotal