MCP_TOOL_TIMEOUT is parsed with a minimum of 1 and ENABLE_MCP_LARGE_OUTPUT_FILES only disables when explicitly false.
What's wrong with this entry?
MCP and main-loop code no longer reads environment variables directly with hand-rolled parsing. MCP_TOOL_TIMEOUT is now parsed as an integer with a minimum of 1 instead of a bare greater-than-zero check, and the large-output-files guard now only kicks in when ENABLE_MCP_LARGE_OUTPUT_FILES is explicitly false rather than on any truthy string.
CLAUDE_AGENT_SDK_MCP_NO_PREFIXmoves to the same typed lookup.
MCP_TOOL_TIMEOUT
Strings lifted out of the shipped bundle, so the claim above can be checked against them.