T08 · Insecure Dependencies
- Location
SKILL.md:28- Finding
Undisclosed Third-Party Gateway for World Bank Data
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 28-42
Vulnerability Type: Untrusted third-party service dependency
Risk Level: MediumThe skill represents itself as providing access to World Bank indicators, but directs all tool requests to
gateway.pipeworx.io, which is not an official World Bank domain.bash curl -X POST https://gateway.pipeworx.io/worldbank/mcp \ -H "Content-Type: application/json" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_gdp","arguments":{"country_code":"IN"}}}'json { "mcpServers": { "worldbank": { "url": "https://gateway.pipeworx.io/worldbank/mcp" } } }Technical Analysis
The configured endpoint introduces a third-party service into the data supply chain without disclosing or explaining that trust boundary. Although HTTPS protects data in transit, it does not protect requests or responses from the gateway operator itself or from a compromise of that service.
The gateway can observe countries, indicators, date ranges, and other submitted parameters. It can also return inaccurate, manipulated, or schema-valid but misleading data. No response provenance, integrity verification, endpoint authentication beyond ordinary TLS, or direct comparison against the official World Bank API is documented.
There is no evidence in the audited file that the gateway executes code locally or receives credentials. The identified exposure is limited to the confidentiality of submitted queries and the integrity and availability of returned data.
Attack Path
- A user installs the provided MCP configuration.
- The MCP client sends World Bank queries to
https://gateway.pipeworx.io/worldbank/mcp. - The gateway operator, or an attacker who compromises the gateway, records the submitted query metadata.
- The gateway returns manipulated, incomplete, stale, or fabricated indicator values while preserving ...[truncated 816 chars]
- Remediation
View remediation
Remediation Suggestions
- Replace the intermediary with the official World Bank API wherever technically possible.
- If the gateway is required, explicitly disclose that queries are processed by Pipeworx and document its ownership, privacy policy, retention practices, and security controls.
- Restrict accepted responses to a documented schema and validate country codes, indicator codes, date fields, numeric values, and response-size limits.
- Verify returned values against the official World Bank source when data integrity is important.
- Pin the service to an approved endpoint and enforce HTTPS certificate validation, strict redirect handling, and conservative request timeouts.
- Do not send credentials, personal data, confidential research parameters, or other sensitive information through the gateway unless appropriate contractual and technical protections are established.
- Document failure behavior so unavailable or unverifiable data is reported as such rather than treated as authoritative.
