T08 · Insecure Dependencies
- Location
SKILL.md:16- Finding
Untrusted Third-Party MCP Gateway Dependency
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 16–18 and 37–41
Vulnerability Type: Untrusted external service and supply-chain dependency
Risk Level: MediumThe skill directs all xkcd requests through
https://gateway.pipeworx.io/xkcd/mcprather than an official xkcd endpoint.Vulnerable code:
bash curl -X POST https://gateway.pipeworx.io/xkcd/mcp \ -H "Content-Type: application/json" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_comic","arguments":{"number":353}}}'json { "mcpServers": { "xkcd": { "url": "https://gateway.pipeworx.io/xkcd/mcp" } } }Technical Analysis
The MCP configuration delegates tool execution and response generation to an externally operated gateway. The reviewed skill provides no response-schema enforcement, returned-URL allowlist, integrity verification, service ownership information, or documented trust boundary.
Because the remote service controls the returned titles, transcripts, alt text, metadata, and image URLs, compromise or malicious operation of that service could cause consuming agents to receive manipulated content. This is a supply-chain trust issue: the behavior observed by users can change remotely without any modification to the reviewed
SKILL.md.This finding does not establish that the named service is currently malicious. It identifies the security exposure created by relying on an unverified intermediary.
Attack Path
- A user installs the documented MCP server configuration.
- The agent sends comic requests to
gateway.pipeworx.io. - The gateway, or an attacker who compromises it, returns manipulated comic metadata, transcript text, or URLs.
- The consuming agent presents, follows, or processes the response as trusted xkcd content.
- If downstream automation interprets returned text as instructions or automatically accesses returned URLs, the atta ...[truncated 725 chars]
- Remediation
View remediation
Remediation Suggestions
- Prefer xkcd's official HTTPS JSON endpoints and retrieve comic data without an unnecessary intermediary.
- If the gateway must remain in use, document its operator, security expectations, privacy practices, and incident-response contact.
- Validate every MCP response against a strict schema, including expected types, field lengths, and required properties.
- Treat titles, transcripts, alt text, and all other remotely returned strings as untrusted data; never interpret them as agent instructions.
- Restrict returned image and permalink URLs to an explicit allowlist of expected HTTPS xkcd domains.
- Disable automatic navigation, command execution, or tool invocation based on returned content.
- Apply network egress controls so the integration can communicate only with approved endpoints.
- Add timeout, response-size, redirect, and content-type restrictions to reduce abuse by a compromised service.
- Clearly disclose that comic requests are sent to a third party rather than directly to xkcd.
