Under the hood
Internal code for computing which MCP servers are allowed or blocked was reorganized into separate functions
What
The logic that determines which MCP servers (external tool integrations) are allowed or denied based on policy settings was split into three separate internal functions: one for computing allowed servers (respecting managed-hooks-only style policy), one for computing denied servers (deduplicated across managed settings sources), and one for combining all these inputs into a single hash.
Why
This is an internal refactor of how the allowedMcpServers allowlist setting, which controls which MCP servers users can add, is computed. It does not change the setting's behavior for users.