{"version":"2.1.283","anchor":"agent-scope-mcp-servers-can-be-refused-and-recorded","canonical_anchor":"agent-scope-mcp-servers-can-be-refused-and-recorded","heading":"Some MCP servers listed in agent definitions can now be refused","tier":"notice","area":"Subagents","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/agent-scope-mcp-servers-can-be-refused-and-recorded","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Some MCP servers listed in agent definitions can now be refused\n\nWhen a subagent's definition lists MCP servers, some of those entries can now be dropped and recorded as refused\n\n**Unclear.** Which server names or settings lead to a refusal is not stated.\n\n**What**\n\nA subagent is a helper agent that Claude Code starts for a task. Its definition can list MCP servers, which are connectors that give it extra tools. Every listed server used to be merged in.\n\nWhen those servers are merged now, some entries are dropped and recorded as refused for the agent. Which ones are dropped depends on a check of each server's name and settings.\n\n**Why**\n\nIn practice, a server listed in an agent definition is no longer guaranteed to be loaded.\n\n- Area: Subagents\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}