{"version":"2.1.277","anchor":"one-mcp-connector-tool-marked-non-backgroundable","canonical_anchor":"one-mcp-connector-tool-marked-non-backgroundable","heading":"One MCP-connector tool marked non-backgroundable","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/one-mcp-connector-tool-marked-non-backgroundable","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### One MCP-connector tool marked non-backgroundable\n\nAn internal MCP connector lookup tool can no longer run in the background\n\n**Unclear.** The finding does not say what would go wrong if the tool ran in the background, only that it is now disallowed.\n\n**What**\n\nAn internal tool that resolves MCP (Model Context Protocol, a way of connecting external tools and data sources to Claude) connector payloads by a directory identifier is now marked as never backgroundable. This means it can't be run in a background context, such as inside a subagent (a separate Claude instance spawned to do a sub-task).\n\n**Why**\n\nRestricting this tool to run only in the main session context suggests it depends on state that isn't reliably available, or safe to use, outside that context.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}