What it does
readonly-sql-guard is intended to make an agent's database access read-only. It inspects what a statement calls, not just its shape, to look for write operations, DDL, side effects and transaction escapes. The publisher describes this as making read-only access provable.
It is meant for cases where an agent runs caller-supplied SQL against a production, ERP or analytics database, such as a query MCP tool, a text-to-SQL feature or an admin console. It is also meant for reviewing database-access code for write, DDL, side-effect or transaction-escape risks.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- AI Templates (aitmpl) first seen 13 Nov 2026 · last seen 17 Nov 2026 · its page on the source · figures reported by the source: aitmpl downloads 2
readonly-sql-guard
Make an agent's database access provably read-only. Use when an agent runs caller-supplied SQL against a production/ERP/analytics database (a "query" MCP tool, text-to-SQL, an admin console), or when reviewing DB-access code for write/DDL/side-effect/transaction-escape risks. Checks what a statement CALLS, not just its shape.
As shown on www.aitmpl.com when we last read it