# Claude Code 2.1.305 loads MCP servers your allowlist left out

> Claude Code 2.1.305 stops allowedMcpServers filtering managed-mcp.json stdio servers that use ${VAR} only in env, so one you left out now loads on upgrade.

- URL: https://acceptallhq.com/diff/2026-10-21-claude-code-2-1-305-mcp-allowlist/
- Section: The Diff
- Published: 2026-10-21T07:04:00-04:00
- Author: MK (https://acceptallhq.com/about/)
- Tool: Claude Code
- Source: https://code.claude.com/docs/en/changelog

## What changed

Claude Code 2.1.305, released October 20, changes how `allowedMcpServers` applies to `managed-mcp.json`. Stdio servers that use `${VAR}` only in `env` are no longer filtered by the allowlist: a server your allowlist left out loads on upgrade, and `deniedMcpServers` is the way to keep it off. Plugins that Claude Desktop mounts by path no longer keep their `allowed-tools` when managed settings set `allowManagedPermissionRulesOnly`. A new `sandbox.allowNestedUserNamespaces` setting lets sandboxed commands on Linux create user namespaces, for Chromium and rootless podman, which lets them get around the sandbox's file protections.

## Why it matters if you ship with an agent

If an admin pushes managed-mcp.json and your allowlist was doing the filtering, a server you never approved loads after this upgrade. Run `claude mcp list` after updating and add a `deniedMcpServers` entry for anything that should stay off. Leave the nested-namespaces setting alone unless a sandboxed command needs it; it opens the file protections by design.
