v4.1.15 makes Cline's MCP toggle auto-approve everything

Cline released version 4.1.15 on August 23, fixing a bug in its "Use MCP servers" toggle that had made the setting nearly pointless. Before this build, checking the box only mattered if you'd also approved each MCP tool individually, so most people who turned it on saw no change in behavior and assumed it did nothing.

Cline's v4.1.15 release notes say the toggle alone auto-approves every MCP tool call across every connected server in this version, with no per-tool opt-in required. Anyone who left the box checked because it seemed inert inherits a wider unattended tool surface after updating to v4.1.15.

MCP servers can reach file systems, shell commands, and third-party APIs, depending on what's connected. A setting that goes from mostly decorative to granting everything, with no security-specific callout, is easy to miss inside a general bug-fix release.

The same build fixed a second, unrelated issue. For custom OpenAI-compatible models, Cline had been inferring the model's capability list and stripping every tool from the request without saying so. Version 4.1.15's release notes list this alongside the MCP fix, giving a custom model integration that seemed to get worse over recent releases a documented explanation.

Neither bug was cosmetic. One made a permission toggle lie about what it approved. The other made a model lose tools it was supposed to have, with no error to explain why.

People running Cline with MCP servers connected should open the toggle's current setting and confirm what it's approving before leaving it running unattended.