T09 · Insecure Skill Coding Practices
- Location
pipeline-mcp.yaml:5- Finding
Unauthenticated Network Endpoint Permits Abuse of the Operator's OpenAI API Account
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill does sentiment scoring as advertised, but its HTTP mode can expose an unauthenticated endpoint that spends the operator's OpenAI API quota.
Review the HTTP/MCP mode before installing or running it. Use the CLI mode for local-only use, or change the server to bind to localhost and put any remote deployment behind authentication, request-size limits, rate limits, and OpenAI spending controls. Do not submit sensitive text unless you are comfortable sending it to OpenAI.
pipeline-mcp.yaml:5Unauthenticated Network Endpoint Permits Abuse of the Operator's OpenAI API Account
The pipeline forwards raw stdin content directly to an external OpenAI API as the user message, which can expose sensitive data entered at the CLI to a third-party service. Because this file contains no notice, consent mechanism, redaction, or input restrictions, operators may unknowingly transmit secrets, personal data, or proprietary content off-host.
The pipeline forwards arbitrary user-supplied text to the external OpenAI API, and this file shows no disclosure, consent, or data-handling controls around that transfer. This creates a real privacy and compliance risk because users may submit sensitive content that is transmitted to a third party without clear warning or minimization.
This manifest identifies the skill name and type but does not describe when it should be invoked or what specific user phrases or contexts should activate it. For manifest files, missing specificity on trigger scope can lead to ambiguous or overly broad invocation behavior if activation is inferred elsewhere.
No suspicious patterns detected.