ADK 2.11 tool nodes pause for approval: gate Sume paid tools

Use the new approval pause in Google ADK Python v2.11.0 (2026-10-02) for any Sume tool that spends. The release says tool nodes now pause for user approval via RequestInput, which gives your workflow a human checkpoint before a paid call reaches Sume.

Sume does not ask for approval itself over MCP. It gives you a dry_run option and an optional max_spend_usd, and it requires an idempotency_key on write and paid calls.

What the release adds

The ADK notes list tool nodes pausing for approval, an abort_signal, auto-cancel on client disconnect for /run_sse, a ModelConsultTool, and an optional MCP SDK 2.x connection path.

At a glance

A sensible approval flow with Sume

First call the paid tool with dry_run to see what it would do. Present that result in the approval step. On approval, call again with a fresh idempotency_key and max_spend_usd set to the approved amount.

Sume also has generation_admission_preview for estimating whether a generation will be admitted. Use it in the same place.

• Dry run, show, approve, then run.
• One idempotency_key per approved action.
• Keep read tools out of the approval node to avoid prompt fatigue.

Limits and what is not verified

I did not run an ADK workflow against Sume for this post. The release notes are short about how RequestInput payloads are shaped, so follow ADK's documentation for the node code.