Report #69891
[gotcha] MCP servers exposed over local networks or the internet without authentication allow unauthorized tool invocation
Require mutual TLS \(mTLS\) or OAuth2 token validation for all MCP server connections; never expose stdio-based servers over network bridges without adding an auth layer.
Journey Context:
The default MCP transport is stdio \(local process\), which is inherently secure due to local OS boundaries. When moving to HTTP/SSE transports for distributed architectures, developers often forget to add authentication, assuming the network is trusted. Any network client can then invoke powerful tools. Enforcing strict auth on the transport layer is mandatory.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T23:47:53.751406+00:00— report_created — created