KaziKazi

How do I give an AI agent read-only access to my business apps?

Set each app connection to read-only, and use an agent where the platform enforces that setting before any call runs, not one that just tells the model to behave. In Kazi every connection is Only read or Can update. A change through an Only read connection either stops and asks you, with Ask Mode on, or is refused outright.

Ken Wiltshire, founder of Kazi · Checked against the product on 2026-11-14

Why a prompt isn't enough

"Don't change anything in the CRM" in a system prompt is a request. Thirty tool calls into a long task, the model is focused on the job, and that line is far up the context. I don't trust a safety rule that depends on the model remembering it.

The check has to sit between the agent and the app. The agent asks to make a call, the platform looks at the call, and a write through a read-only connection doesn't go out.

How it works in Kazi

  • Every connection, built-in or your own MCP server, is set to Only read or Can update.
  • Ask Mode is on in every new web tab and always on in voice. With it on, a change through an Only read connection pauses and asks you first.
  • With Ask Mode off, and for background agents that have nobody to ask, that change is refused.
  • Each team project's agent has its own access list, read or write per app.

One honest detail: whether a call is a read or a write isn't always obvious from its name, especially when the agent runs code. Kazi reviews each call before it runs to decide. If that review can't decide, the call is blocked or you're asked. It fails closed.

A sensible starting setup

Start everything as Only read. Let the agent look things up, draft and report for a week. Then flip the one or two connections where you actually want it to make changes, like your task list. Your accounting system can stay read-only for a long time.