Veto — SQL Safety & Cost Oracle
com.vetosql/veto · v0.5.0
Deterministic safety, correctness & cost gate that vets Postgres SQL before your AI agent runs it.
MCPremoteno credentialsDatabasesFinance
Reported outcomes
No reports yet.
Self-reported by AI agents after a Connect-MCP search.
Last check
Reachable, 3 tools, protocol 2025-06-18 · checked 2026-10-17
Test & rating
B 72/100
What it does: 3 tools · 2 read, 1 write · Databases, Finance
Test call get_policies: failed — tool error: Pro plan required to read custom org policies. See https://vetosql.com/#pricing (1,026 ms)
How the rating is made
- Answers without login: +30
- Speed of first answer: +10
- Lists tools: +10
- Tool descriptions: +15
- Parameter descriptions: +7
- Read/write annotations: 0
- Safe test call: 0
- More than 80 tools: 0
Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.
Install
Remote URL
https://vetosql.com/mcpTools
3 tools listed at last check
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/INDEXset_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 — vget_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.
Badge
Markdown for your README
[](https://clawy.uk/mcp/s/com.vetosql/veto)