This setting keeps a list of MCP servers that stay disabled, even if they’re configured in the project.
It’s a blocklist approach: most servers remain available and only the flagged ones are blocked.
That lets you cut off sensitive integrations, like broad system or network access, without shutting down the whole MCP ecosystem.
When to use
- When some MCP servers have risky capabilities you’d rather keep off.
- To lock specific integrations in shared environments.
- As a security control without disabling every MCP.
How to use
Apply the setting and edit the blocklist with the server names you want to block.