Mistral Vibe: "Approve for Session" Now Grants Whole-Tool Trust
Mistral VibeMistral Vibe changed what a single "Approve for session" decision authorizes when Smart Approve gates a call to an MCP or connector tool: the grant now covers the whole tool, not just the exact arguments a developer reviewed, so calling the same connector tool again with different arguments no longer re-prompts. Built-in tools are unaffected and keep their narrower per-call approval scope. The change shipped in v2.25.1 alongside other Smart Approve hardening in the same release, and it widens the practical trust granted by a single approval for tools that reach outside the local workspace into services like GitHub, Slack, Notion, and Gmail.
Key Takeaways
- "Approve for session" now covers an entire MCP or connector tool, not just the specific arguments a developer reviewed when granting approval.
- Calling the same connector tool again with different arguments no longer re-prompts, once it has been approved once in a session.
- Built-in Vibe tools are unaffected, they keep the narrower per-call approval scope they always had.
- The change widens the practical trust granted by a single click, since connector tools can reach external services like GitHub, Slack, Notion, and Gmail.
- It shipped in v2.25.1 (2026-09-09) alongside other Smart Approve hardening in the same release.
- Developers who rely on "Approve for session" for fine-grained control should re-audit that assumption, since one approval now stands in for the whole tool for the rest of the session.
Broader Trust From a Single Click
Mistral Vibe changed what a single "Approve for session" decision actually grants when Smart Approve mode gates a call to an MCP or connector tool. Previously, that approval was scoped to the exact arguments of the call being approved: asking the same tool again with different arguments triggered a fresh approval prompt, even within the same session. As of v2.25.1, approving a connector tool for the session now covers the whole tool, not just the specific arguments in front of the user at approval time. Calling that tool again later in the session, with any arguments, no longer re-prompts.
Built-In Tools Keep Their Narrower Scope
The change applies only to MCP and connector tools. Mistral Vibe's built-in tools (the file, shell, and editing tools shipped with the CLI itself) keep their existing per-call resolver scope, so approving one built-in call does not implicitly authorize every future call to that same built-in tool. The distinction matters because connectors reach outside the local workspace, into services like Notion, Linear, Slack, GitHub, Gmail, and Google Calendar, so a single approval now stands in for trust across an entire class of actions a connector's tool can take, not just the one action a developer actually reviewed.
Why It Matters
The tradeoff is explicit: fewer interruptions for developers who lean on connectors repeatedly in one session, at the cost of a wider blast radius per approval. A developer who approves a GitHub connector's "create issue" call with one set of arguments is, from that point on, also pre-approving every other argument combination for that same tool for the rest of the session, without a second look. Mistral Vibe shipped the change alongside several other Smart Approve fixes in the same v2.25.1 release, part of a broader push that release to tighten and clarify the boundary between what a session can do automatically and what still needs a human's sign-off. Anyone relying on "Approve for session" as fine-grained, per-call trust should treat it, going forward, as authorization for the whole tool.