fix: properly handle custom guardrails parameters

[Harshit28j]

Relevant issues

Fixes #18718

Pre-Submission checklist

Please complete all items before asking a LiteLLM maintainer to review your PR

• I have Added testing in the tests/litellm/ directory, Adding at least 1 test is a hard requirement - see details
• 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

CI (LiteLLM team)

CI status guideline:

• 50-55 passing tests: main is stable with minor issues.
• 45-49 passing tests: acceptable but needs attention
• <= 40 passing tests: unstable; be careful with your merges and assess the risk.

• Branch creation CI run
  Link:

• CI run for the last commit
  Link:

• Merge / cherry-pick CI run
  Links:

Type

🐛 Bug Fix

Changes

Solution

Modified initialize_custom_guardrail to extract all parameters from litellm_params using model_dump() and pass them via **extra_params to the custom guardrail constructor. Parameters that are already handled explicitly (guardrail, mode, default_on) are excluded.

Files Changed

• litellm/proxy/guardrails/guardrail_registry.py - Added logic to pass all litellm_params to custom guardrail init

[vercel]

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

Project	Deployment	Review	Updated (UTC)
litellm	Ready	Preview, Comment	Jan 12, 2026 7:35pm