T08 · Insecure Dependencies
- Location
SKILL.md:21- Finding
Unaudited Third-Party MCP Gateway for UN Comtrade Operations
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 21-29
Vulnerability Type: Third-party service and supply-chain trust risk
Risk Level: Mediumjson { "mcpServers": { "comtrade": { "url": "https://gateway.pipeworx.io/comtrade/mcp" } } }Technical Analysis
The skill represents itself as an interface to UN Comtrade but configures an external MCP service hosted at
gateway.pipeworx.io, rather than an official UN Comtrade endpoint. The project contains no locally auditable implementation, authentication policy, service-integrity controls, ownership verification, or disclosure of how queries and responses are handled.HTTPS protects network traffic in transit but does not establish that the service operator or returned MCP content is trustworthy. The remote provider can observe submitted trade queries and controls the tool responses consumed by the agent. If the provider, its infrastructure, or its dependencies are compromised, the endpoint could return inaccurate data or adversarial content designed to influence subsequent agent behavior.
Attack Path
- A user or agent loads the MCP configuration from
SKILL.md. - The agent connects to
https://gateway.pipeworx.io/comtrade/mcp. - Trade queries and associated parameters are transmitted to the third-party service.
- The service observes those queries and generates the corresponding MCP responses.
- A malicious or compromised service returns manipulated trade data or adversarial response content.
- The agent may trust, summarize, or act on the manipulated response as though it originated from an authoritative UN Comtrade source.
Impact Assessment
The third-party gateway can access trade-query data sent through the configured MCP connection and control the content returned for the advertised tools. This creates confidentiality and integrity risks, including query monitoring, inaccurate trade results, a ...[truncated 375 chars]
- A user or agent loads the MCP configuration from
- Remediation
View remediation
Remediation Suggestions
- Replace the third-party gateway with an official UN Comtrade endpoint where technically possible.
- Alternatively, include a locally auditable MCP implementation that communicates directly with the authoritative data source.
- If the gateway is required, document its operator, ownership, privacy policy, retention behavior, and security responsibilities.
- Obtain explicit user consent before transmitting queries or other potentially sensitive context to the service.
- Restrict the MCP integration to explicitly approved tools and validate response schemas, sizes, and content types.
- Treat returned text as untrusted data and prevent it from being interpreted as agent instructions or executable content.
- Apply endpoint allowlisting, certificate validation, authentication, logging, timeout limits, and appropriate network egress restrictions.
- Independently verify security-sensitive or decision-critical trade results against authoritative UN Comtrade data.
