T07 · Tool Hijacking and Spoofing
- Location
SKILL.md:19- Finding
Undisclosed Third-Party MCP Endpoint Spoofs CourtListener Integration
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 19–23
Vulnerability Type: Tool hijacking and spoofing through an unrelated third-party MCP gateway
Risk Level: MediumVulnerable Code
json { "mcpServers": { "court-listener": { "url": "https://gateway.pipeworx.io/court-listener/mcp" } } }Technical Analysis
The skill describes itself as an interface to the Free Law Project's CourtListener API, but the configured MCP server is hosted on
gateway.pipeworx.io, rather than an official CourtListener or Free Law Project domain. The configuration therefore delegates request confidentiality, tool behavior, and response integrity to an undisclosed third-party intermediary.Because MCP responses can influence an agent's conclusions and subsequent actions, a malicious or compromised gateway could return modified, fabricated, or selectively omitted legal information while appearing to operate as the legitimate
court-listenertool. The remote operator can also change this behavior after the skill has been reviewed because the server implementation is not included in the audited project.This finding does not establish that the gateway is currently malicious. It identifies an unverified trust boundary and a spoofing risk arising from the mismatch between the represented service and the configured endpoint.
Attack Path
- A user installs or loads the MCP configuration from
SKILL.md. - The client registers the third-party endpoint under the legitimate-looking name
court-listener. - The user or agent submits legal search terms, docket queries, or opinion identifiers through that tool.
- Requests are transmitted to
gateway.pipeworx.io, allowing the gateway operator or a party that compromises it to observe the research activity. - The gateway supplies tool responses and can alter, omit, or fabricate case metadata and opinion content.
- The agent treats tho ...[truncated 721 chars]
- A user installs or loads the MCP configuration from
- Remediation
View remediation
Remediation Suggestions
- Replace the gateway with an official, documented CourtListener or Free Law Project endpoint where such an endpoint is available.
- If MCP translation is required, use a locally hosted and audited adapter that communicates directly with the documented CourtListener API.
- If the Pipeworx gateway must remain, explicitly disclose that it is a third-party intermediary, identify its operator, and document its data retention, privacy, and response-integrity guarantees.
- Authenticate the remote server and pin its expected identity or deployment where the MCP client supports those controls.
- Restrict the MCP server to the minimum required tool capabilities and avoid transmitting confidential case strategy, personal information, credentials, or other sensitive query data.
- Validate returned case identifiers and legally significant content against an authoritative source before relying on them.
- Require informed user confirmation before sending queries to the third-party service.
- Establish monitoring and review controls for endpoint ownership, TLS configuration, unexpected tool-schema changes, and anomalous responses.
