{"version":"2.1.248","anchor":"mcp-environment-variables-parsed-once-with-bounds","canonical_anchor":"mcp-environment-variables-parsed-once-with-bounds","heading":"MCP environment variables parsed once, with bounds","tier":"use","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/mcp-environment-variables-parsed-once-with-bounds","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### MCP environment variables parsed once, with bounds\n\nMCP_TOOL_TIMEOUT is parsed with a minimum of 1 and ENABLE_MCP_LARGE_OUTPUT_FILES only disables when explicitly false.\n\n**What**\n\nMCP 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.\n\n**Details**\n\n- `CLAUDE_AGENT_SDK_MCP_NO_PREFIX` moves to the same typed lookup.\n\n**Evidence**\n\n`MCP_TOOL_TIMEOUT`\n\n- Area: MCP\n- Names: `MCP_TOOL_TIMEOUT`, `ENABLE_MCP_LARGE_OUTPUT_FILES`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}