com.vetosql/veto · v0.5.0 · data-and-databases
Veto — SQL Safety & Cost Oracle is healthy: it completed an MCP handshake in 1209 ms and exposes 3 tools.
Deterministic safety, correctness & cost gate that vets Postgres SQL before your AI agent runs it.
Endpoint: https://vetosql.com/mcp (streamable-http)
Repository · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 3 |
| Latency | 1209 ms |
| Last checked (UTC) | 2026-10-16T01:15:14.019Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-16T01:15:14.019Z | Healthy | 1209 | |
| 2026-10-14T22:45:34.436Z | Healthy | 2126 |
analyze_sql | Analyze Postgres SQL/migrations for destructive operations, locking risk, correctness traps (NULL handling that silently returns wrong results), anti-patterns, and query cost. Returns a deterministic verdict (ok/warn/block) with findings. Pass the optional `schema` argument (your CREATE TABLE/INDEX |
set_policies | Replace the stored custom org policy set for your Pro key (this is also how you update or clear them: send the full new set to update, or an empty array to remove all). Each policy blocks or warns on an operation against matching tables (e.g. no DELETE on payments). Policies are declarative data — v |
get_policies | Return the custom org policy set currently stored for your Pro key — the same rules analyze_sql enforces on top of the built-ins. Read-only; returns an empty list if none are set. Use set_policies to change them. |