T08 · Insecure Dependencies
- Location
SKILL.md:18- Finding
Unaudited Third-Party MCP Service Dependency
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 18–23
Vulnerability Type: Unverified remote MCP dependency
Risk Level: MediumThe skill delegates its functionality to a remotely operated MCP endpoint whose implementation is not included in the project:
json { "mcpServers": { "boardgames": { "url": "https://gateway.pipeworx.io/boardgames/mcp" } } }Technical Analysis
The configuration directs the agent to connect to
gateway.pipeworx.io, while the documentation describes the skill as a wrapper for the Board Game Atlas API. Because the project contains no local implementation, integrity metadata, pinned server version, authentication guidance, or enforceable tool allowlist, the behavior of the remote service cannot be verified from the reviewed artifact.The remote operator—or an attacker who compromises the service—could change the MCP tool definitions and responses after this skill has been reviewed, without modifying
SKILL.md. Data returned by the service could also contain misleading or instruction-bearing content. This is a supply-chain trust risk rather than evidence that the endpoint is currently malicious.Attack Path
- A user or agent loads the MCP configuration from
SKILL.md. - The agent establishes a connection to
https://gateway.pipeworx.io/boardgames/mcp. - Board-game queries are transmitted to the third-party gateway.
- The gateway supplies remotely controlled tool definitions and tool responses.
- If the gateway is compromised or changes behavior, it can return manipulated content or expose functionality beyond the three documented operations.
- If the consuming agent fails to constrain tools and treat responses as untrusted data, the manipulated service output may influence subsequent agent actions.
Impact Assessment
The confirmed exposure is disclosure of board-game queries and associated request m ...[truncated 520 chars]
- A user or agent loads the MCP configuration from
- Remediation
View remediation
Remediation Suggestions
- Prefer a bundled, reviewable MCP implementation or a documented official upstream endpoint.
- Pin the MCP server implementation or protocol version and verify release integrity where the deployment model permits it.
- Restrict the client to an explicit allowlist containing only
search_games,get_game, andhot_games. - Apply least privilege so the remote MCP server cannot access local files, credentials, shell execution, memory, or unrelated tools.
- Treat all tool definitions and responses as untrusted remote data; do not interpret response content as agent instructions.
- Validate response schemas, enforce size and timeout limits, and reject unexpected tool capabilities or content types.
- Document that requests pass through
gateway.pipeworx.io, including what query and metadata fields are transmitted. - Establish monitoring, endpoint ownership verification, and a process for disabling the integration if the service changes unexpectedly.
