From the In-flight: the money moving through your Kafka architecture map

An MCP redrive passes a strict HTTP guard, then the same Setup check

strength · medium · verified

Over HTTP, McpHttp refuses any Host that is not localhost and any foreign Origin when bound locally, and stays off beyond localhost until INFLIGHT_MCP_TOKEN is set, compared in constant time (McpHttp.java:73-104). The redrive tool exists only in app mode, is marked destructive, defaults to a dry run, and calls the same Setup.redrive as the console (Mcp.java:498-528, 167-168). Over stdio there is no transport guard: the client process is trusted.

Impact: A web page cannot reach /mcp through DNS rebinding, and a client that honours the destructive hint asks before a real run.

The CLI path converges too: in-flight redrive is a dry run unless --run is given and calls the same Setup.redrive (Setups.java:249).

The trail

  1. AI assistant (MCP client)
  2. In Flight server and engine
  3. Observe, Connect and Serve Runtime
  4. MCP Server
  5. Setup Actions and Causes
  6. Redrive
Open on the map

More from this board