other
- Location
SKILL.md:32- Finding
Undisclosed Transmission of User Queries Through a Third-Party Gateway
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 32–56
Vulnerability Type: Undisclosed third-party data disclosure
Risk Level: LowThe skill states that it is powered by Datamuse, but its documented requests transmit user-provided words and phrases to
gateway.pipeworx.io, a separate third-party intermediary.Vulnerable Code
bash ## Example: find rhymes for "code" curl -X POST https://gateway.pipeworx.io/words/mcp \ -H "Content-Type: application/json" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"find_rhymes","arguments":{"word":"code","limit":10}}}' ## Example: words meaning "ocean" that start with "s" curl -X POST https://gateway.pipeworx.io/words/mcp \ -H "Content-Type: application/json" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"find_words","arguments":{"meaning_like":"ocean","spelled_like":"s*"}}}' { "mcpServers": { "words": { "url": "https://gateway.pipeworx.io/words/mcp" } } }Technical Analysis
The examples and MCP configuration direct all word-search requests to Pipeworx. This conflicts with the introductory representation that the toolkit is powered by the Datamuse API, because the documentation does not explain Pipeworx's role as an intermediary.
Queries are placed in JSON request bodies and can include arbitrary user-provided words or phrases. Pipeworx can consequently receive the submitted text and associated network metadata. If a user enters confidential text while seeking synonyms, related terms, or autocomplete results, that information may be disclosed outside the expected trust boundary.
No evidence indicates that credentials, local files, system data, or executable payloads are sent. The reviewed file also contains no local executable code.
Attack Path
- A user or agent loads the documented MCP server configuration.
- The user supplies a word or phrase to a word-search operation.
- The client serializes that in ...[truncated 911 chars]
- Remediation
View remediation
Remediation Suggestions
- Clearly identify Pipeworx as the service receiving requests and explain whether it proxies Datamuse.
- Document what query content and metadata are transmitted, retained, logged, or shared.
- Obtain explicit user consent before transmitting potentially sensitive text to the third-party gateway.
- Where feasible, use the official Datamuse endpoint directly to reduce unnecessary intermediaries.
- Advise users not to submit secrets, credentials, personal data, or confidential text.
- Provide a privacy policy and data-retention policy for the configured gateway.
- If the gateway is required, apply contractual and technical controls covering encryption, retention limits, access control, deletion, and incident response.
