fix(proxy/ui): handle guardrail blocks without traceback and restore policy attachment delete action

[markwilson0761]

Relevant issues

N/A

Pre-Submission checklist

• I have Added testing in the tests/test_litellm/ directory, Adding at least 1 test is a hard requirement
• My PR passes all unit tests on make test-unit
• My PR's scope is as isolated as possible, it only solves 1 specific problem
• I have requested a Greptile review by commenting @greptileai and received a confidence score >= 4/5

Type

🐛 Bug Fix

Changes

This PR includes 2 targeted bug fixes:

1. Prevent traceback noise for expected guardrail block behavior

• Proxy now treats guardrail-triggered 4xx blocks as policy rejections (expected outcome), instead of surfacing full traceback in error_information.
• This keeps guardrail block responses clean and user-facing behavior consistent.

2. Fix policy attachment delete action in Dashboard UI

• Restored delete icon click handling for policy attachments in the Policies page.
• Verified from proxy-served UI (localhost:4000) that clicking delete now triggers the expected removal flow.

Also included updated proxy-served UI static build artifacts under:

• litellm/proxy/_experimental/out/**

Validation

• Manually reproduced and verified both issues locally:
  • Guardrail block no longer exposes traceback.
  • Policy attachment delete icon now responds correctly in UI.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
litellm	Ready	Preview, Comment	Mar 21, 2026 5:10pm

[greptile-apps]

Too many files changed for review. (441 files found, 100 file limit)

[CLAassistant]

All committers have signed the CLA.

[codspeed-hq]

Merging this PR will not alter performance

✅ 16 untouched benchmarks

---

_{Comparing markwilson0761:litellm_fix_error_handle (6bb4b94) with main (d8e4fc4)}