T08 · Insecure Dependencies
- Location
skill.json:26- Finding
Unpinned Third-Party npm Package Is Downloaded and Executed Automatically
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill’s agriculture knowledge-search purpose is coherent, but it includes broad organizational export, automatic conversation logging, and an unpinned executable MCP dependency that receives the API token.
Install only if you trust the UPLO instance, the npm package publisher, and the administrators who can access logged or exported data. Use a narrowly scoped, revocable API token; avoid sensitive sessions unless logging is acceptable; and prefer a pinned or otherwise verified MCP server package before production use.
skill.json:26Unpinned Third-Party npm Package Is Downloaded and Executed Automatically
SKILL.md:41Conversation Summaries Are Transmitted Without Consent or Data-Minimization Controls
SKILL.md:31Full Organizational Context Export Violates Least-Privilege Design
The skill is presented as a knowledge search and structured extraction tool, but it also instructs the agent to export full organizational context and log conversations. Those capabilities materially expand data access and retention beyond the stated purpose, creating a risk of unnecessary disclosure of internal organizational data and collection of user conversation content without clear need or scoping.
Session-end conversation logging is not clearly necessary for an agricultural knowledge-search skill, so it introduces avoidable data collection. If used broadly, it could capture sensitive operational, compliance, or personnel-related details from conversations and store them in another system without a defined business justification.
The skill instructs automatic conversation logging at session end without any user-facing notice or consent mechanism. In a domain involving agricultural operations, compliance records, and possibly employee or livestock data, this can result in silent retention or export of sensitive conversation content and metadata, undermining privacy expectations and increasing regulatory and internal-data-handling risk.
This manifest requires an API token and injects it into the MCP server environment, while also configuring an HTTP endpoint for the service. The file describes the capability and token requirement, but it does not warn users that the skill will use credentials and communicate with a remote UPLO instance.
The markdown shows users placing an API_KEY in configuration, but it does not include any warning about protecting secrets or avoiding accidental disclosure. Because this skill connects to an external service and uses credentials, a brief user-facing warning would improve safe setup and reduce the chance of mishandling sensitive information.
No suspicious patterns detected.