Research review / frameworks

ADK Removes Implicit Session Sharing From MCP Prompt Arguments

An ADK Python change committed November 17 UTC removes a path that let MCP prompt declarations select session-state values. Developers must explicitly provide arguments; the checked stable release predates this change.

By Sandeep Belgavi · Published 2026-11-18

Google's ADK Python commit 889ddd3 landed at 21:56 UTC on November 17, 2026, or November 18 in India. It changes McpInstructionProvider so an MCP server's declared prompt arguments no longer determine which session values are sent to that server.

Remote argument names selected local state

The removed code fetched prompt definitions, collected their argument names and selected matching keys from session state. That made a server-controlled declaration influence local data disclosure. The commit describes a malicious or compromised server requesting sensitive values by choosing matching names.

The replacement accepts a developer-supplied arguments mapping or a callable that constructs one from context. With no explicit arguments, it sends none. The accompanying tests cover the default and both explicit modes. This is a code-level hardening change; the source does not establish that an exploitation incident occurred.

Migration status matters

The change is marked breaking because prompts that previously depended on automatic argument population need explicit configuration. At access time, the repository's latest published release was v2.14.1, published November 12, before this commit. A package version should therefore be checked for inclusion of the fix rather than assumed protected because it is the latest stable tag.

Make the data boundary observable

Original proposed exercise, not executed: populate a mock session with display_mode=compact and a dummy sentinel under private_marker. Let a mock prompt declare both names. Observe the outbound arguments before and after applying an explicit allowlist containing only display_mode.

The acceptance condition is that the sentinel never reaches the mock server, even when the remote declaration changes. Also confirm that the intended display option still arrives. This checks both confidentiality and the migration's functional behavior.

An explicit callable can still disclose too much if it copies the entire state. Review the selection logic as part of the boundary. ADK's Apache-2.0 license was checked; this article reproduces no implementation code and reports no local SDK test results.

Sources accessed November 18, 2026. Views are my own and do not represent any employer, past or present.

Sources and evidence

Let application code select the prompt data sent to an MCP server, and verify that the deployed ADK build contains this still-unreleased change.