Overview
LiteLLM provides comprehensive guardrails to ensure safe, compliant, and policy-compliant LLM usage. Guardrails can inspect and moderate content before and after LLM calls, block inappropriate requests, and enforce custom policies.What are Guardrails?
Guardrails are hooks that:- Pre-call: Validate inputs before sending to LLM
- Post-call: Validate outputs before returning to user
- During call: Monitor streaming responses in real-time
- Block requests/responses
- Modify content
- Log policy violations
- Alert on issues
Built-in Guardrails
LiteLLM includes several pre-built guardrail integrations:Azure Content Safety
Azure Prompt Shield
Protect against prompt injection attacks:Aporia AI Guardrails
LlamaGuard
Custom Guardrails
Create your own guardrail logic:Basic Custom Guardrail
Post-Call Guardrail
Streaming Guardrail
Guardrail Modes
Pre-Call Mode
Validate before sending to LLM:- Input validation
- Prompt injection detection
- PII detection in prompts
- Rate limiting by content
Post-Call Mode
Validate after LLM response:- Output content filtering
- PII redaction
- Fact checking
- Citation verification
During-Call Mode
Monitor streaming responses:- Real-time content moderation
- Stop generation early
- Token-by-token filtering
Guardrail Configuration
Default On/Off
Content Masking
Violation Messages
Advanced Guardrail Features
Modify Response Exception
Return synthetic response instead of blocking:Session-Based Guardrails
Track violations across a session:Logging Guardrail Events
Best Practices
Guardrail Recommendations
- Layer multiple guardrails - Combine different detection methods
- Use pre_call for speed - Block bad inputs early
- Use post_call for accuracy - Inspect actual LLM output
- Monitor performance - Track guardrail latency
- Test thoroughly - Verify guardrails don’t block valid requests
- Log violations - Track what’s being blocked and why
- Set appropriate thresholds - Balance safety vs. false positives
Common Patterns
Multi-Layer Safety
PII Protection Pipeline
Industry Compliance
Performance Considerations
Async Guardrails
Always use async methods for better performance:Parallel Guardrails
Multiple guardrails run in parallel when possible:Caching Guardrail Results
Troubleshooting
Guardrail Not Triggering
High Latency
False Positives
Related Features
- Logging - Track guardrail events
- Cost Tracking - Monitor guardrail costs
- Fallbacks - Handle guardrail failures