Do You Know How Many MCP Servers Are Running in Your Environment Right Now?

Most organizations have no idea how many MCP servers are running in their environment—and attackers are counting on that.

In this clip, Adrian Culley breaks down the exact steps security teams need to take now: run the network scan, apply stringent code review to every MCP server project you find, and mandate authentication. Authorization may be optional in the MCP spec—but it doesn't have to be optional in your deployment.

Any MCP server touching sensitive or regulated data needs identity-aware proxy enforcement, mutual TLS, and RBAC before it stays in production. Every tool invocation should be logged with parameters and identity, correlated against behavioral baselines, and integrated into your SIEM.

If you can't identify an anomalous tool call within an hour of it occurring, your dwell time is too long for this threat surface.