Skip to content
MCP server

Veto — SQL Safety & Cost Oracle

By vetosqlAll Vetosql servers

Deterministic safety, correctness & cost gate that vets Postgres SQL before your AI agent runs it.

Listed on

First seen 2 Oct 2026. One server, whatever directories list it: each directory listing keeps its own page and history.

2
Directories
1 via MCP Toplist
3
Tools
From an anonymous probe
-
ToolBench grade
Not graded by Arcade
0
GitHub stars
From MCP Toplist

Tools

ToolDescriptionBehaviour
analyze_sqlAnalyze 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 DDL) to also get EXPLAIN-based cost analysis run on a throwaway scratch Postgres — no separate tool or DB connection needed.Not declared
get_policiesReturn 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.Not declared
set_policiesReplace 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 — validated, never executed — and apply transparently to every later analyze_sql call made with this key. Use get_policies to read the current set.Not declared

Directory listings

DirectoryListingTierFirst seen
Official MCP RegistryVeto — SQL Safety & Cost Oracle-2 Oct 2026
PulseMCPListed there according to MCP Toplist’s dataset; not collected by InvokeRank.