What You’ll Accomplish
Guardrails let you block dangerous queries before they execute. You can:- Prevent accidental
UPDATEorDELETEwithout aWHEREclause - Block
DROP TABLEand other destructive DDL commands - Enforce read-only access for specific user groups
- Require
LIMITclauses on large tables - Block queries that access sensitive columns
The Problem Guardrails Solve
Without guardrails, one typo can destroy production data:How Guardrails Work
Rule Types
| Type | Description | Use Case |
|---|---|---|
| Input Rules | Evaluate the query before execution | Block dangerous commands |
| Output Rules | Evaluate results after execution | Redact sensitive data in output |
Guardrails vs Other Features
| Feature | Purpose | When to Use |
|---|---|---|
| Guardrails | Block queries based on patterns | Prevent dangerous operations |
| Live Data Masking | Redact sensitive data in output | Protect PII in query results |
| Access Requests | Require approval for access | Time-limited or command-level approval |
| Access Control | Control who can access resource roles | Restrict resource role visibility |
- Guardrails block
DROP TABLEcommands - Live Data Masking redacts SSN in
SELECTresults - Access Requests require approval before connecting
- Access Control limits who sees the resource role
Ready to set it up? The Guardrails configuration guide covers prerequisites, creating rules, pattern syntax, actions, recipes, testing, and troubleshooting.
Next Steps
Guardrails Configuration
Detailed configuration options and rule syntax
Live Data Masking
Automatically redact sensitive data in query results
Access Requests
Require approval for access to sensitive resource roles
Session Recording
Audit all query executions including blocked queries