T08 · Insecure Dependencies
- Location
skill.json:25- Finding
Unpinned Third-Party Package Is Automatically Downloaded and Executed
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill appears purpose-built for UPLO energy knowledge search, but it combines sensitive energy-sector data access with broad export/logging capabilities and an unpinned auto-downloaded MCP server.
Install only if you trust the UPLO MCP server package and can use a least-privilege UPLO token. Prefer a pinned, reviewed MCP package version, verify the endpoint is HTTPS, confirm server-side authorization/classification controls, and avoid full organizational exports or conversation logging unless your role and retention policy explicitly allow them.
skill.json:25Unpinned Third-Party Package Is Automatically Downloaded and Executed
skill.json:42Broad Organizational Context Export Conflicts with Least-Privilege Access
The README advertises an export_org_context tool that can produce a full organizational context snapshot, but it does not warn users about the sensitivity of exported data or the privacy and access-control implications. In a knowledge-management product for energy-sector records, this increases the risk of inadvertent bulk disclosure of internal, confidential, or restricted operational information by normalizing export capability without cautionary guidance.
The skill explicitly instructs use of log_conversation to create an auditable record of compliance evidence assembly, but it does not warn the user that their prompts, summaries, and tool usage may be retained as a durable record. In this energy-sector context, those logs can contain sensitive operational, regulatory, cybersecurity, or CEII-adjacent details, creating privacy, confidentiality, and compliance risk if users are not informed and data minimization is not enforced.
The skill requires a secret API key and connects to a remote HTTP MCP endpoint, but the manifest provides no user-facing disclosure about credential use, remote transmission, or what data may be sent off-platform. In a power/grid intelligence context, this increases the risk of sensitive queries, documents, or operational context being transmitted to an external service without informed consent.
The manifest exposes an export_org_context capability even though the stated purpose is knowledge search and retrieval. That materially broadens the data-access surface to include bulk organizational context export, which could enable unnecessary exfiltration of sensitive operational, regulatory, or safety-related information from an energy-sector environment.