Join our Newsletter — 33% off our NHI Course

Could an MCP proxy on 8080 trust internal WebSocket access?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20225
Topic starter  

TL;DR: A reachable MCP proxy can accept WebSocket connections on port 8080 without revalidating the original caller, according to Tego AI. Internal segmentation and upstream controls therefore carry the real burden for who can reach private tools.

Editorial analysis by NHI Mgmt Group, based on content published by Tego AI: “Inside Anthropic's MCP tunnels”.

Key questions

Q: Why do internal MCP tunnels create risk even when the edge is authenticated?

A: Because the edge and the proxy are not the same control point.

Q: How should teams audit MCP traffic when the proxy forwards plaintext to the upstream server?

A: They should capture tool calls at the proxy-to-upstream hop, not just tunnel lifecycle events.

Q: What breaks when an MCP proxy is reachable from inside the network without reauthentication?

A: The public authentication boundary stops protecting the private path.

Practitioner guidance

  • Isolate the MCP proxy from lateral network reach Allow only the tunnel daemon and approved control-plane components to reach mcp-proxy:8080.
  • Require upstream authentication for every MCP server Make OAuth or an equivalent upstream control mandatory on each private MCP server so that a caller who reaches the proxy still cannot invoke tools without separate authorization.
  • Instrument the proxy-to-upstream hop Log tool names, arguments, responses, and caller context at the point where the proxy forwards requests to the private server, because edge lifecycle logs alone do not show actual tool use.

Bottom line: The central risk is not the tunnel itself, but the gap between edge authentication and internal proxy trust.

Glossary terms: MCP tunnel, Proxy Trust, Delegated Support Authority, Internal segmentation

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 1 week ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20715
 

Authentication that ends at the edge is not end-to-end authentication. The article shows that the tunnel validates the caller before the proxy, but the proxy itself does not re-run those checks. That means the real trust boundary is not the public hostname, it is the internal network path to mcp-proxy:8080. Practitioners should treat edge identity as necessary but insufficient when a private proxy can still be reached from inside the environment.

A few things that frame the scale:

  • 24,008 unique secrets were exposed in MCP configuration files in 2025 alone, the protocol's first year of widespread adoption, according to the State of Secrets Sprawl 2026.

A question worth separating out:

Q: Should organisations treat MCP proxies as privileged infrastructure or simple routing components?

A: They should treat them as privileged infrastructure. The proxy is the point where routed identity, policy, and visibility all converge, so a weakly protected proxy can become a hidden control plane for private tool access. Routing alone is not a sufficient security model when the proxy can impersonate the trusted caller.

👉 Read our full editorial: MCP tunnels leave reauthentication to internal network controls


This post was modified 1 week ago by NHI Mgmt Group

   
ReplyQuote
Share:

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.