{"version":"2.1.265","anchor":"waitformcpservers-tool-refactored-to-a-create-based-factor","canonical_anchor":"waitformcpservers-tool-refactored-to-a-create-based-factor","heading":"WaitForMcpServers tool refactored to a create()-based factory and drops its explicit auto-allow checkPermissions","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/waitformcpservers-tool-refactored-to-a-create-based-factor","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### WaitForMcpServers tool refactored to a create()-based factory and drops its explicit auto-allow checkPermissions\n\nInternal tool that waits for MCP servers was rebuilt as a factory function and no longer auto-allows itself\n\n**Unclear.** The `tengu_mcp_pending_call` gate mentioned alongside this change is unread, so nothing can be said about whether it is switched on.\n\n**What**\n\nThe internal tool that waits for MCP servers (external tool providers connected via the Model Context Protocol) to become available was restructured from a plain object into a factory function that produces the tool. It also dropped its own explicit permission check that always automatically allowed itself, and now looks up connected servers through a different internal method.\n\n**Why**\n\nThis is an internal restructuring of how this tool is built and how it checks for available servers, rather than a change in what it does for users.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}