8 views
-/https://github.com/berriai/litellm/issues/14516
GitHub · issue

#14516 [Bug]: Setting "output_parse_pii" has no effect

  • State: open
  • Author: @metalshanked
  • Labels: bug

### What happened?

Tried setting output_parse_pii as True with presidio but the response is still masked I tried setting it in the UI, config.yml and even in the completion request as below

``` { "model": "mymodel", "messages": [ {"role": "user", "content": "my name is jane doe"} ], "guardrails": ["pii_mask"], "guardrail_config": {"output_parse_pii":false}

} ```

RESPONSE -- STILL MASKED

``` choices": [ { "finish_reason": "stop", "index": 0, "message": { "content": "Hello, <PERSON>! How can I assist you today?", "role": "assistant", "annotations": [] }, "provider_specific_fields": { "content_filter_results": { "hate": { "filtered": false, ```

### Relevant log output

```shell

```

### Are you a ML Ops Team?

No

### What LiteLLM version are you on ?

1.77.1

### Twitter / LinkedIn details

_No response_

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (1 events)
#0 of 0 · 31d17h51m9s ago — entered · #import:https:::github.com:berriai:litellm post #3001
Issue 27982 spans proxy request accounting, Redis caching/transactions, persistence, and UI filtering, creating broader cross-layer debugging and regression risk. Issue 14516 is comparatively localized to guardrail configuration propagation and output handling.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search