A Guth Labs publication ↗
Back to News

Vercel fixes approval replay so validation cannot rewrite the action that was approved

Vercel fixes approval replay so validation cannot rewrite the action that was approved

Vercel’s November 13 AI SDK 7.0.173 release fixes a subtle approval boundary: validating or refining a tool call must not change the arguments a person has already approved. The patch prevents in-place schema validation and input refinement from mutating those arguments during approval replay. Official release

The associated commit says approval continuation could previously alter tool inputs and message history during revalidation. Its change isolates validation from the original data and preserves the approved input. The author reports regression tests and live provider checks for generation and streaming, with workflow approval behavior covered by existing tests. Those are maintainer-reported checks, not an independent audit. Implementation and test account

The companion workflow 2.0.105 release also adds a configurable approval policy. Its toolApproval setting overrides an individual tool’s needsApproval setting; approved calls can execute without pausing, while denied calls return an execution-denied result. The release adds separate total, per-step, first-output and between-chunk timeout controls. Workflow release

Guth analysis

Approval is meaningful only if the executed action is the approved action. A confirmation screen cannot provide that guarantee if later parsing silently rewrites the payload. This patch addresses that particular boundary; it does not establish that every application using the SDK has safe policies.

Builders should also notice the precedence rule. A centralized workflow policy may simplify governance, but it can override a tool-level approval expectation. Tests should exercise approval replay, policy overrides and cancellation, not only successful execution.

Evidence limits

No independent reproduction, exploitation claim or affected-version range was established here. The article describes the November 13 release and its maintainers’ stated tests, not a newly discovered incident or a universal security guarantee.

Sources and citations

Revision history

Published .