An AI vendor’s agent, reading a customer’s on-prem database. Approved, read-only, on the record.
Acme Muhasebe is an accounting office. Its ERP database sits on a server in its office, with no inbound ports open. FinBot sells an agent that reconciles invoices. Below is the real state of that setup on tunr.sh right now. The company names and numbers are made up; the connector, grants, read-only enforcement and audit trail are the production system.
Acme’s office server
The connector inside Acme’s network.
- Site
- istanbul-office
- Status
- online connected 5h 13m ago
- Connector
- tunr 0.8.0, outbound only
- End-to-end TLS
- sha256 705521b3b9522a28938f568f…
- Resource
- acme-muhasebe/erp-db postgres≤ 500 rows/query5 q/sAcme's Logo ERP: customers (cari), invoices (fatura), payments (tahsilat), stock (stok). Read-only.
Access requests
What FinBot’s agents asked for, and what Acme decided.
What the agent actually ran
Connections and query summaries for the latest grant (acme-muhasebe/erp-db). Full query text is off: Acme keeps only the command, tables, rows and timing.
The agent hasn’t connected yet.
Acme’s audit log
Decisions, connections and blocked statements, newest first. Individual connection open/close events are left out here; people are shown by role (the real log names them).