feat: surface guardrail denial reason in 446 error message - #1740
Open
Idooran wants to merge 1 commit into
Open
Conversation
When a webhook guardrail denies a request, the 446 error message now includes the reason returned by the webhook (e.g. "Guardrail denied the request: Dlp") instead of the generic "The guardrail checks defined in the config failed" message. This extracts the reason/message from the webhook's responseData or explanation fields and surfaces it in the top-level error.message, making it much easier for developers and end-users to understand why their request was blocked without digging into hook_results. Falls back to the original generic message when no specific reason is available. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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
1 participant
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
When a guardrail webhook denies a request, the 446 error message is hardcoded to
"The guardrail checks defined in the config failed"— which gives the end user zero context about why the request was denied.This PR extracts the denial reason from the webhook's response data and surfaces it in the error message. For example, instead of:
Users now see:
Changes
src/handlers/handlerUtils.ts: AddedextractGuardrailDenyMessage()that walkshook_resultsto find denial reasons fromresponseData.reason,responseData.message, orexplanationfields. Falls back to the original message if no reasons are found.src/handlers/responseHandlers.ts: Uses the new function for the after-request-hook 446 path.Backward Compatibility
responseData.reason,responseData.message, andexplanationin order, accommodating different webhook response shapes.