Canonical: https://instain.ru/en/ai/nvidia-nemo-guardrails/ Language: en NVIDIA rule library for applications with models # NVIDIA NeMo Guardrails. Programmable rules for model inputs, outputs, and actions 4.30 / 5 [Directory score](https://instain.ru/en/ai/nvidia-nemo-guardrails/#editorial-rating) [Official website ](https://docs.nvidia.com/nemo-guardrails/) The developer sets checks around the application with the model and chooses which inputs, outputs or actions to handle separately. The rules should be checked with examples. ![NVIDIA Guide to Rules for Language Model Applications](https://instain.ru/assets/images/nvidia-nemo-guardrails-screen-a7e7a64bfcbe-1200.webp) NVIDIA Guide to Rules for Language Model Applications. [Open the source ](https://docs.nvidia.com/nemo-guardrails/) ## First, describe the boundary in words. The training manual assistant should explain the order of the application and can show an example. A separate permit is required to change the application. In NeMo Guardrails, checks are configured around the model and application. First, identify the permitted actions and where they need to be checked. At the input, you may need to check the topic, at the output, check the response form, and before turning to the tool, a separate rule for its arguments. ## Check permission and refusal Write pairs of requests that differ in one meaningful condition. For one pair, ask for an explanation of the return policy, then ask the assistant to issue a return on the user's behalf. Add harmless questions that use words from prohibited examples. This exposes both missed violations and false positives. Record the response and actual tool calls. A refusal message does little good if the application still passed the data to the tool. ## Separate verification from authorization Control the credentials and permissions of connected systems separately. For the training check, use stubs and fictional entries to ensure that the result of the erroneous classification remains visible in the journal. When changing the model or template of the dialogue, repeat successful and borderline cases. Consider the delay of additional checks and find out what happens when they fail. The decision to block or transfer to the operator must be understandable and reproducible. Start with a short run, where you can name a specific rule for each refusal. ## Suitable tasks - Check the processing of the request outside the specified topic - Track failure before transferring data to tool Features ## Strengths - Rules can be described programmatically - The official repository contains configuration examples Things to consider ## Limitations - A rule can miss a violation or block a permitted request - Restrict tool permissions separately ## Selection and conditions Free access Yes Trial period Not confirmed No sign-up required Not confirmed Russian interface Not confirmed Local installation Yes API Not confirmed “Not confirmed” means there is not enough information. The feature may still be available; check the developer’s terms. Input formats Text, Code Result Text, Data ### Terms The toolkit is open source. Selected models, extra checks, and hosting can incur charges. A rule can miss a violation or block a permitted request. From task to first result ## Practical example Task Check the processing of the request outside the specified topic What to prepare A test copy of the assistant and a fictional read and write policy. ### Task brief or prompt Run regular and border requests. Check that the valid reading is working, and the action without permission is not in the journal. ### Expected result Report with inputs, observed actions and comments to the rules. ### How to check the result - Check the tool log separately from the response text. - Test only in an agreed environment. An editorial teaching example of a task brief, not the result of hands-on testing of the service. Check that the required mode is available, that you have rights to the source material and that the intended use of the result is permitted. Check details ## Official sources - [NVIDIA NeMo Guardrails ](https://docs.nvidia.com/nemo-guardrails/) - [NeMo Guardrails official repository ](https://github.com/NVIDIA-NeMo/Guardrails) This description is based on the developer’s material. Features, prices and availability may change; check the primary source before use. About the tool Developer NVIDIA Category [Code](https://instain.ru/en/category/code/) Access You need a compatible environment, an application with a language model, and a configuration for your rules. Some checks require another model. Payment The toolkit is open source. Selected models, extra checks, and hosting can incur charges. API No separate API specified [Developer terms ](https://github.com/NVIDIA-NeMo/Guardrails) Directory score 4.30 / 5 Features 4.40 / 5 Workflows 4.00 / 5 Ecosystem 4.40 / 5 Documentation 4.40 / 5 Scores are an editorial guide to the directory. They are not user reviews or the results of personal testing. [See the methodology ](https://instain.ru/en/methodology/) Keep exploring ## For similar tasks [Full category ](https://instain.ru/en/category/code/) Code ### [Promptfoo](https://instain.ru/en/ai/promptfoo/) Repeatable checks for applications with language models 4.40 / 5 AI Application Security Checker Tool Similar tasks; compare terms, formats and limitations Code ### [Inspect AI](https://instain.ru/en/ai/inspect-ai/) Tasks with defined inputs, steps, and result checks 4.38 / 5 Framework for Language Model Assessment Similar tasks; compare terms, formats and limitations