feat(plan): enforce strict read-only policy and halt execution on violation #16849
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.

Summary
This PR refines the experimental Plan Mode by implementing a strict "secure-by-default" policy that allows only read and search operations. It also enhances the tool scheduler to immediately halt agent execution if a prohibited tool is attempted, preventing retry loops and providing clear guidance to the user.
Closes #16625
Details
Policy Implementation
packages/core/src/policy/policies/plan.tomlwith a default-deny rule for all tools in Plan mode.read_file,web_fetch,google_web_search, etc.) only.Execution Control
CoreToolSchedulerto return aSTOP_EXECUTIONerror type when a tool is denied in Plan mode.How to Validate
Build the project:
Run in Plan Mode:
# Ensure experimental.plan is enabled in your settings npm start -- --approval-mode=planAttempt a Write Operation:
Attempt a Read Operation:
Pre-Merge Checklist