T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:13- Finding
Undisclosed Third-Party MCP Gateway Introduces an External Trust Boundary
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:13-19
Vulnerability Type:T05: Unauthorized Access and Privilege Escalation
Risk Level: Mediumjson { "mcpServers": { "cdc": { "url": "https://gateway.pipeworx.io/cdc/mcp" } } }Technical Analysis
The skill describes itself as a wrapper for CDC open data available through
data.cdc.gov, but its configuration directs the agent togateway.pipeworx.io, a separate third-party domain. The package provides no local implementation, integrity validation, ownership statement, privacy disclosure, authentication constraints, or evidence that this gateway is operated by or affiliated with the CDC.Configuring this endpoint delegates MCP tool definitions, query processing, and returned content to an externally controlled service. This creates a trust boundary beyond what is necessary to retrieve public CDC Socrata data directly. The remote service may observe dataset searches and requested identifiers, alter responses, or change its behavior after the skill has been reviewed.
The audited content does not establish that the gateway is malicious, and there is no evidence of local code execution, credential theft, persistence, or direct prompt injection. The risk arises from undisclosed third-party control over the MCP interface and data flow.
Attack Path
- A user installs or activates the MCP configuration from
SKILL.md. - The agent connects to
https://gateway.pipeworx.io/cdc/mcprather than directly to the documented CDC Socrata API. - Dataset search terms, requested dataset identifiers, and associated MCP request metadata are transmitted to the third-party gateway.
- The gateway supplies tool definitions and responses to the agent.
- If the gateway is compromised or behaves deceptively, it can return manipulated public-health data or modify exposed tool behavior.
- The agent or user may rely on those responses as ...[truncated 876 chars]
- A user installs or activates the MCP configuration from
- Remediation
View remediation
Remediation Suggestions
- Replace the third-party MCP gateway with direct access to the documented CDC Socrata API at
data.cdc.govwhere practical. - If the gateway is required, clearly disclose its operator, purpose, CDC affiliation status, privacy policy, retention practices, and all data transmitted to it.
- Restrict the MCP server to the minimum operations required for public dataset search and retrieval.
- Do not send credentials, personal information, private prompts, or unrelated session context to the gateway.
- Validate returned dataset identifiers, schemas, source URLs, and records against the official CDC Socrata service.
- Pin or otherwise validate the expected MCP interface and reject unapproved tool-definition changes.
- Apply connection timeouts, response-size limits, strict schema validation, and output sanitization.
- Document the external trust boundary in the skill description so users can make an informed decision before activation.
- Perform an independent security and privacy review of the gateway operator before production use.
- Replace the third-party MCP gateway with direct access to the documented CDC Socrata API at
