{"version":"2.1.299","anchor":"agent-tools-allowlist-supports-mcp-server-wildcards-with-a","canonical_anchor":"agent-tools-allowlist-supports-mcp-server-wildcards-with-a","heading":"Agent tool lists can include every tool from an MCP server, and warn on misses","tier":"use","area":"Subagents","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/agent-tools-allowlist-supports-mcp-server-wildcards-with-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Agent tool lists can include every tool from an MCP server, and warn on misses\n\nA tools entry naming an MCP server or ending in `__*` now expands to that server's tools, with a warning if none match\n\n**What**\n\nAn agent definition can list which tools the agent may use. An entry that names an MCP server (an add-on that gives extra tools), or ends in `__*`, now expands to all of that server's tools. If no connected server of that name has any tool, Claude Code warns that the entry takes no tool. Before, such entries matched on the server name only and gave no warning.\n\n**Why**\n\nA mistyped server name in an agent's tools list now shows up as a warning instead of silently giving the agent nothing.\n\n- Area: Subagents\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}