
ADK's tool confirmation feature lets a tool pause and wait for a yes or no from a user or a supervising system before it runs. Some agent actions should wait for a person before executing, and the Professional Agentic Architect exam focuses on how ADK enforces that pause at the framework level rather than leaving it to the model. Getting the design right comes down to configuring confirmation selectively, knowing how approval responses return to ADK, accounting for current session service limits, and separating pre-execution confirmation from instructions and callbacks.
To require approval before a tool runs, wrap the function in a FunctionTool and set its require_confirmation parameter. The parameter accepts two forms:
True, which pauses every call to the tool for approval before it runs.The choice between True and a function depends on whether every invocation requires human review. Setting require_confirmation to True pauses every call, including routine calls that should proceed automatically. Passing a function lets the framework evaluate the tool's arguments on each call, such as checking whether a value exceeds a threshold, so routine calls go through automatically while calls that meet the condition pause for approval. Because FunctionTool handles the pause directly, the framework enforces the rule with minimal custom code.
Once a tool call pauses for confirmation, ADK waits for a yes or no answer before running the function. That response comes back through either of two paths:
adk_request_confirmation call.Either path delivers the approval decision from a user or a supervising system back to the paused tool before the action runs.
Tool confirmation in ADK is experimental, and that status carries a compatibility constraint that matters for the Professional Agentic Architect exam. The feature does not yet support DatabaseSessionService or VertexAiSessionService. Setups that rely on tool confirmation run with ADK's in-memory session service instead. When reviewing an architecture that combines tool confirmation with a session backend, confirm that the selected session service is supported.
Two alternative patterns are often considered for human oversight, and neither provides the same pre-execution enforcement as require_confirmation:
after_tool_callback: a callback that notifies someone runs only after the tool has already executed, so the notification arrives too late to stop an action that has already happened.When an action requires human approval before it runs, we would wrap the tool in a FunctionTool with require_confirmation rather than relying on model instructions or post-execution notifications. That keeps enforcement in the framework and ensures the pause happens before execution.
Our Professional Agentic Architect practice exams test ADK tool confirmation alongside ADK session services and tool callbacks, with detailed explanations that drill these distinctions.