Under the hood
Internal tool that waits for MCP servers was rebuilt as a factory function and no longer auto-allows itself
What
The 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.
Why
This 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.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
The `tengu_mcp_pending_call` gate mentioned alongside this change is unread, so nothing can be said about whether it is switched on.