Repository navigation
docs: clarify MCP policy approval requirements for permit rules - #26562
Open
dave123981 wants to merge 2 commits into
Open
dave123981 wants to merge 2 commits into
dave123981 wants to merge 2 commits into
Conversation
✅ Deploy Preview for docsdocker ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
dave123981
changed the title
This branch has not been deployed
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.
Description
Clarifies the relationship between approval-required outcomes and regular
permitstatements in the MCP policy reference.The existing wording suggests that an approval-required outcome is a separate decision that takes precedence over a normal
permit. However, approval-required behavior is applied to apermitthrough the@requireApprovalannotation.This change:
permitwith@requireApprovalreturns an approval-required outcome instead of immediately allowing the request.forbiddenies the request without elicitation.Related issues or tickets
Closes #26560
Reviews