Secure SQL proxy for AI agents — NL→SQL, AST safety, per-agent RLS, audit log.
Secure SQL proxy between AI agents and enterprise databases. Agents call a single endpoint in plain English (or structured SQL). QueryShield: 1. Translates natural language → SQL via Claude with prompt caching. 2. Validates every query at the AST level — only is allowed, no stacked statements, no forbidden functions, LIMIT required. 3. Applies per-agent row-level security: schema/table whitelists…
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
Secure SQL proxy between AI agents and enterprise databases. Agents call a single endpoint in plain English (or structured SQL). QueryShield: 1. Translates natural language → SQL via Claude with prompt caching. 2. Validates every query at the AST level — only is allowed, no stacked statements, no forbidden functions, LIMIT required. 3. Applies per-agent row-level security: schema/table whitelists and 4. Executes against the customer DB and returns rows. 5. Logs every attempt to an append-only…
Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.