Swap the connection string
Point your database host at the Vericto proxy. No code changes, no extra dependencies.
postgres://user:pass@proxy.vericto.com:5432/workspace/dbDatabase guardrails for AI agents
Say yes to AI agents on production data.
Vericto checks each SQL statement before it reaches your database: destructive ones come back blocked with a fix, sensitive columns come back masked, and every decision is signed. Deterministic: same statement, same rules, same verdict.
vericto-proxy
$ INCOMING query from llm-agent:
DELETE FROM users;
BLOCKED — Rule: VERICTO-001
AST: DeleteStmt > WhereClause = NULL
Estimated rows affected: 15,420
Suggested fix: DELETE FROM users WHERE id = $1
Added: ~0.08 ms per statement (p50, measured)
10M+
queries analyzed
~0.08 ms
added per statement (p50, measured)
0
false positives
4
SQL dialects
How it works
Three-step integration. No agents, no SDKs, no code changes.
Vericto parses the AST in real time
Every query goes through the Vericto AST parser (pg_query + sqlparser-rs). The syntax tree is evaluated against the active ruleset in process: the proxy adds about 0.1 ms per statement at the median (measured on dedicated EC2, small statements).
DeleteStmt > WhereClause = NULL → BLOCKEDDestructive queries blocked, safe ones pass
Queries that violate the rules are blocked with a descriptive error. Safe queries pass transparently through to your database.
VERICTO-001: DELETE with no WHERE — 15,420 rows protected