This tutorial helps you build a reusable guardrail profile that protects both inputs and outputs for a production-facing deployment.Documentation Index
Fetch the complete documentation index at: https://budecosystem-b7b14df4.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
What You Will Build
A guardrail profile that:- Uses Bud Sentinel probes for safety and PII categories.
- Applies both input and output guard types.
- Uses a tuned severity threshold.
- Deploys to an existing project deployment.
Prerequisites
- Access to Bud AI Foundry.
- A project with at least one active deployment.
- Permission to create and deploy guardrails.
Step 1: Start the Workflow
- Go to Guardrails.
- Click + Add Guardrail.
- Confirm you can access the provider selection screen.
Step 2: Choose Provider and Probes
- Select Bud Sentinel.
- Click Next.
- Search probe catalog with tags (for example, Safety and PII).
- Select the probes you need.
- Review probe details to validate coverage.
Step 3: Choose Deployment Type
Select Add to Existing Deployment so the profile protects an already-running endpoint.Step 4: Choose Project and Deployment
- Pick your target project.
- Select the deployment/endpoint you want to protect.
- Continue to profile configuration.
Step 5: Configure the Profile
Set:- Name:
production-safety-guardrail - Guard Types:
input,output - Severity: start at medium and tune based on observed traffic
- Description: add policy intent and owner team
Step 6: Deploy
- Click Deploy.
- Wait for the success state.
- Open the guardrail detail page and validate:
- selected probes
- active deployment mapping
- status and timestamps
Step 7: Validate with Test Prompts
Use known-safe and known-risk prompts to verify behavior and reduce false positives/negatives before broad rollout.Best Practices
Start with a narrow probe set and expand incrementally.
Use medium thresholds first, then tune using real traffic.
Document profile intent and ownership in descriptions.
Review deployment mappings after each release.
Revalidate policy after probe catalog updates.