langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-22 20:45:26 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Guardrail Node #20970

New Issue
Open
opened 2026-02-21 20:10:03 -05:00 by yindo · 3 comments
yindo commented 2026-02-21 20:10:03 -05:00
Owner
Copy Link
Copy Source

Originally created by @DavideDelbianco on GitHub (Dec 11, 2025).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report, otherwise it will be closed.
  • Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

Related to #19606

  • The old moderation model has been terminated by OpenAI
    Image

  • The new omni-moderation model supports image moderation
    Image

  • Version 1.11.0 introduced support for multimodal image embedding

  • Not all models support built-in guardrails (Azure / AI Foundry does, Open AI doesn't)

  • The current "moderation" feature cannot be used anywhere, especially in embedding pipelines

A new node "Guardrail" could prove useful and be used both before LLM input processing, and after LLM output
To recognize harmful content like Jailbreak, NSFW text and images, but also mask / replace PII, Passwords, Secret keys, remove URLs based on custom criteria (domain, topic, etc..)

2. Additional context or comments

No response

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @DavideDelbianco on GitHub (Dec 11, 2025). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report, otherwise it will be closed. - [x] Please do not modify this template :) and fill in all the required fields. ### 1. Is this request related to a challenge you're experiencing? Tell me about your story. Related to #19606 - The old moderation model has been terminated by OpenAI <img width="805" height="296" alt="Image" src="https://github.com/user-attachments/assets/587217bd-ab9f-4d80-9918-6ad60c29ff39" /> - The new omni-moderation model supports image moderation <img width="1287" height="577" alt="Image" src="https://github.com/user-attachments/assets/4984db26-18ce-4caf-be17-b59de83e8a6a" /> - Version 1.11.0 introduced support for multimodal image embedding - Not all models support built-in guardrails (Azure / AI Foundry does, Open AI doesn't) - The current "moderation" feature cannot be used anywhere, especially in embedding pipelines A new node "Guardrail" could prove useful and be used both before LLM input processing, and after LLM output To recognize harmful content like Jailbreak, NSFW text and images, but also mask / replace PII, Passwords, Secret keys, remove URLs based on custom criteria (domain, topic, etc..) ### 2. Additional context or comments _No response_ ### 3. Can you help us with this feature? - [ ] I am interested in contributing to this feature.
yindo added the 💪 enhancementstale labels 2026-02-21 20:10:03 -05:00
yindo commented 2026-02-21 20:10:03 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jan 11, 2026):

Hi, @DavideDelbianco. I'm Dosu, and I'm helping the Dify team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You proposed a new "Guardrail" node to enhance content moderation and filtering, replacing the deprecated OpenAI moderation model.
  • The node would detect harmful content, mask sensitive data, and filter URLs both before and after LLM processing.
  • It is intended to support multimodal inputs and be usable on platforms without built-in guardrails.
  • There has been no further activity or comments on this proposal since it was opened.

Next Steps:

  • Please let me know if this feature is still relevant to the latest version of Dify by commenting on this issue.
  • If I do not hear back within 15 days, the issue will be automatically closed.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Jan 11, 2026): Hi, @DavideDelbianco. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale. **Issue Summary:** - You proposed a new "Guardrail" node to enhance content moderation and filtering, replacing the deprecated OpenAI moderation model. - The node would detect harmful content, mask sensitive data, and filter URLs both before and after LLM processing. - It is intended to support multimodal inputs and be usable on platforms without built-in guardrails. - There has been no further activity or comments on this proposal since it was opened. **Next Steps:** - Please let me know if this feature is still relevant to the latest version of Dify by commenting on this issue. - If I do not hear back within 15 days, the issue will be automatically closed. Thank you for your understanding and contribution!
yindo commented 2026-02-21 20:10:03 -05:00
Author
Owner
Copy Link
Copy Source

@DavideDelbianco commented on GitHub (Jan 12, 2026):

still relevant n8n introduced it half a year ago

@DavideDelbianco commented on GitHub (Jan 12, 2026): still relevant n8n introduced it half a year ago
yindo commented 2026-02-21 20:10:03 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jan 12, 2026):

@crazywoola The user confirmed the "Guardrail" node feature is still relevant, noting that n8n introduced it half a year ago. Could you please assist with this issue?

@dosubot[bot] commented on GitHub (Jan 12, 2026): @crazywoola The user confirmed the "Guardrail" node feature is still relevant, noting that n8n introduced it half a year ago. Could you please assist with this issue?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label stale 💪 enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#20970
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?