{"version":"2.1.321","anchor":"mcp-denied-tools-setting-parsing-added","canonical_anchor":"mcp-denied-tools-setting-parsing-added","heading":"Claude Code can read a list of MCP tools to deny","tier":"use","area":"MCP","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/mcp-denied-tools-setting-parsing-added","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Claude Code can read a list of MCP tools to deny\n\nClaude Code can now check and merge a list of blocked MCP tools, called mcpDeniedTools, into its settings\n\n**Unclear.** It is not clear where the `mcpDeniedTools` list comes from or whether anything uses it yet.\n\n**What**\n\nMCP tools are extra tools that Claude Code gets from outside programs called MCP servers. Claude Code now has code that reads a list named `mcpDeniedTools` and adds it to its settings when the list is valid. A valid list has to meet these rules:\n\n- Each entry is text made only of allowed characters.\n\n- Each entry has to match the name of an MCP tool.\n\n- The list cannot be longer than a set maximum.\n\n**Why**\n\nThis may be a way, possibly set by an organization or from a remote source, to block particular MCP tools by name.\n\n- Area: MCP\n- Names: `mcpDeniedTools`\n- Tier: Use it now\n- Useful: 5\/5\n- Signal: 4\/5\n- Scope: both\n- Heads-up: no"}