scriptoriumadmin/litellm
1
0
Fork 0
mirror of https://github.com/BerriAI/litellm.git synced 2026-09-22 00:31:44 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 51

docs(release-notes): rewrite guardrail narrative to match release notes style

Browse source
This commit is contained in:
Ishaan Jaffer 2026-02-21 15:02:58 -08:00
parent 789c74e806
commit 226fc6485b
1 changed files with 3 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
docs/my-website/release_notes/v1.81.14.md
View file

@ -53,15 +53,11 @@ pip install litellm==1.81.14
## Guardrail Model Garden
The biggest theme in this release is operationalizing guardrails at scale. The question isn't just "can I turn on a guardrail" — it's "how do I know if my guardrail is working, what happens when it's over-sensitive, and how do I fix it in production without a full redeploy."
This release ships a library of pre-built guardrail policies you can deploy in one click — competitor blockers, topic filters, keyword lists, GDPR/EU AI Act compliance templates, and prompt injection detection. Pick a template, customize the parameters (keyword lists, blocked topics, score thresholds), and attach it to a team or key. No need to write guardrail logic from scratch.
This release ships three things to address that:
Three new built-in guardrails ship alongside the Garden: a competitor name blocker, a topic blocker (keyword and embedding-based), and an insults/keyword filter. All run at the gateway level with no external API call. They're configurable per-team or per-key, and you can swap in AWS Bedrock Guardrails or Azure Content Safety on the same endpoint without changing your application code.
1. **Guardrail Model Garden** — a searchable, categorized library of pre-built policies you can deploy in one click. Competitor blockers, topic filters, keyword lists, GDPR/EU AI Act compliance templates, prompt injection detection, and more. Start from a template and customize, instead of building from scratch.
2. **3 new built-in guardrails** — competitor name blocker, topic blocker (keyword + embedding-based), and insults/keyword filter. All run at the gateway level, configurable per-team or per-key, no external API call required. If you're on AWS Bedrock today and want to add a layer of topic blocking without routing traffic to another service, these work out of the box.
3. **Guardrail tracing** — every request that hits a guardrail now shows the policy name, detection method, and exact match in the logs view. When a policy is firing too aggressively in production, you can see exactly which rule triggered and on what input — instead of guessing.
Guardrail tracing is also included: every request that triggers a guardrail now logs the policy name, detection method, and exact match in the logs view. When a policy fires too often in production, you can see exactly which rule triggered and on what input.
---