docs(vercel_ai): explain privileged tool approval rule - #82
Open
CodingWCal wants to merge 3 commits into
Open
Conversation
Co-authored-by: Cursor <cursoragent@cursor.com>
This was referenced Aug 24, 2026
CodingWCal
marked this pull request as ready for review
August 24, 2026 19:57
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Change
Adds the VAI-013 threat model and rationale for Vercel AI tools that shell out or evaluate dynamic code without a tool-level
needsApprovalgate.Scope boundary
AI SDK 7 moved approval to call or agent-level
toolApproval. The current scanner cannot correlate that setting to a tool, so the document records it as a manual-review limitation.Validation
python tools/check_rulebook.pyadds no new errorsOAI-112,PYD-106Companion PRs
Team
Justin (@jj-javascript): rationale author
Calvin: integration, SDK 7 limitation correction, and final documentation QA
Karlee (@kperpignant): consulting partner, threat model, and QA review (credited contributor)