other
- Location
SKILL.md:19- Finding
Undisclosed Third-Party Exposure of Biomedical Search Queries
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 19–21 and 39–44
Vulnerability Type: Third-Party Data Disclosure
Risk Level: MediumComplete Code Snippet:
bash curl -X POST https://gateway.pipeworx.io/pubmed/mcp \ -H "Content-Type: application/json" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"search_pubmed","arguments":{"query":"CRISPR cancer therapy","limit":5}}}'json { "mcpServers": { "pubmed": { "url": "https://gateway.pipeworx.io/pubmed/mcp" } } }Technical Analysis
The skill is described as providing access to the National Library of Medicine's PubMed database and states that it is powered by NCBI E-utilities. However, both its usage example and MCP client configuration direct requests to
gateway.pipeworx.io, an external intermediary rather than an official NCBI endpoint.Consequently, biomedical search terms are disclosed to that intermediary. Such queries may reveal sensitive medical interests, research activity, or inferred health concerns. The skill provides no information about the gateway's operator, privacy policy, data retention, request logging, response integrity, or operational necessity.
The use of HTTPS protects data in transit from passive network observers, but it does not prevent the gateway itself from reading, retaining, correlating, or modifying requests and responses. The audited file does not establish malicious operation by the gateway; the risk arises from undisclosed third-party processing and the resulting trust boundary.
Attack Path
- A user adds the supplied
pubmedMCP server configuration to an MCP client. - The user or agent submits a biomedical literature query through the advertised tool.
- The client sends the query, request metadata, and associated network metadata to
gateway.pipeworx.io. - The gateway can observe or retain the query and may correlate it with ...[truncated 682 chars]
- A user adds the supplied
- Remediation
View remediation
Remediation Suggestions
- Connect directly to an official NCBI E-utilities endpoint where the client architecture permits it.
- If the intermediary is required, clearly identify it as a third-party data processor and explain why it is necessary.
- Publish or link to its privacy policy, ownership information, retention period, logging practices, security controls, and deletion process.
- Warn users not to submit personally identifiable information, protected health information, unpublished research data, or other sensitive content in search queries.
- Minimize transmitted metadata and disable request logging by default where operationally possible.
- Provide a verifiable self-hosted or official-endpoint alternative.
- Apply response-integrity controls and document how upstream PubMed results are validated against manipulation.
