Gemini CLI 0.62 MCP tool titles: read a Sume call before approving

Gemini CLI 0.62.0, released September 29, 2026, formats MCP tool call titles as structured signatures and separates the explanation from them. On a paid Sume call, read three things in the signature before you approve: the tool name, idempotency_key, and whether dry_run is true.

The Gemini CLI line is from its GitHub releases page, read 2026-10-01. The Sume fields are from tools and gates. I could not see the exact on-screen layout in the release notes, so this post names fields to look for, not a screenshot of the prompt.

What did 0.62.0 change?

The release notes list, under MCP tool formatting: format MCP tool call titles as structured signatures and segregate explanations. The same release retains refresh tokens during credential updates and adds Gemini 3.8 Flash and 3.5 Flash Lite support.

Which fields on a Sume call matter before I approve?

Paid and write tools on hosted MCP require idempotency_key. Three optional fields tell you what approving will do.

Should I approve a call that has no dry_run?

That is a real submit. Sume's docs say ordinary single creates do not need admission theater, but they prefer generation_admission_preview or dry_run before expensive bursts. A good habit is to approve the dry_run=true version first, read the estimate, then approve the real call.

Does approving once cover later calls?

That depends on your Gemini CLI settings, not on Sume. The existing trust setting post explains how trusting a server skips confirmation for its paid tools. Without it, each call is a separate prompt, and a fresh idempotency_key per intent keeps retries from duplicating jobs. Generation admission describes what happens when the workspace is at its concurrency limit.