Synapsor: Adding Review Boundaries to Database Agents
Quantum_CS · reddit · 2026-07-16
The author developed an Apache-2.0 runtime named **Synapsor Runner**, positioned between the MCP client and Postgres/MySQL. It replaces raw SQL tools like `execute_sql` with "reviewed semantic capabilities." The core concept: models can only propose restricted read/write actions, while actual approval and database execution happen outside the model's loop. The system re-verifies tenant scope, target rows, allowed fields, version numbers, idempotency, and affected row counts, logging the receipts. It also supports tiered auto-approvals, two-person approvals, batch restricted writes, and compensation proposals for reversible changes. The author clearly defines its boundaries: it cannot make arbitrary SQL safe, nor can it replace least privilege, restricted views, RLS, or data isolation. It simply tightens the "readable/writable perimeter" to a more auditable level.
Related event: Synapsor Runner Secures AI Database Access(2 posts)→
More from coding & agent
- uv-scripts/ocr returns to the top of Hugging Face datasets with a JSON model picker — vanstriendaniel · 2026-07-21
- Sonar CEO says a guide-verify-solve loop cuts coding-agent issues by 92% — alex_verem · 2026-07-21
- A creator built an Awwwards-style landing page with ChatGPT 5.6 Sol in one conversation — paw_lean · 2026-07-21
- OpenAI’s Build Week buildathon drew 40 people for 11 hours with Codex — paw_lean · 2026-07-21
- Workshop to cover loop and graph engineering for AI-native software engineering — Al_Grigor · 2026-07-21
- Production agents may need a new PaaS layer built around audit and recovery — percoAi · 2026-07-21