5 Questions to Ask Before You Connect AI to Your Business Data

questions before connecting AI to company data -cover

AI is already out of the box in most small business and NPOs we talk to. This is not a post telling you to slow down. We use these tools, our clients use them, and the time they give back is real. This post is about the questions to ask before connecting AI to business data. We present five things worth deciding first.

If you have not yet written down which AI tools your team is allowed to use at all, start with our guide to building an AI usage policy for small business. That post covers the intentions. This one covers what to settle before you grant access to AI.

The five questions

We send a version of these to leadership every time a client asks us to enable an AI tool. They are not technical questions. They are business decisions, and they belong to you rather than to your IT provider:

  • Which company data can staff put into it, and which data is off limits?
  • Will it connect to email, files or chat? If yes, for which staff, and can it act in them or only read?
  • Where does the provider store your data, and do your privacy obligations and client contracts allow that?
  • How will you find out when someone breaks the rule, and what happens next?
  • Which AI tools are your staff already using with company data today?

Most organizations can answer the first four in one meeting. Question two has changed character this year, and question five is the one that stalls teams because of shadow AI. No one knows.

“Can this AI tool read only, or act too?”

There is a line running through every AI deployment, and the line is this: can the tool only read, or can it also do?

Until recently, most AI tools stopped at writing. They read something, produced text, and a person decided what to do with it. Agents do not stop there. An agent files the invoice, updates the customer record, approves the request, changes the setting.

That matters because anything that reads untrusted input and can also take action is an attack surface. Every email your agent reads was written by someone. Most of those someones are customers and suppliers. Some are criminals, and they have worked out that they no longer need to break in. They can ask.

The technique is called indirect prompt injection. Instructions get hidden inside something the agent reads as part of its ordinary work. A PDF invoice. A calendar invite. A shared document. The text can sit in plain sight, white on a white background, and it reads like this:

This is not a fringe concern. Prompt injection is ranked the number one risk in the OWASP Top 10 for LLM Applications (OWASP GenAI Security Project, 2025)

The agent is not hacked. It reads an instruction, cannot tell a stranger’s instruction from yours, and follows it. If it has permission to change banking details, it changes them. Then it marks the task done. That last part is what makes this expensive. Nobody catches it for a week, because the tool reports success and everyone believes the green checkmark. In every other system they have used, a checkmark meant a person had looked.

So when you answer question two, answer it in two halves. What can this tool read, and what can it do? Reading, sorting and summarizing is low risk and worth automating. Moving money, changing bank details, or granting access needs a named person who is accountable, whose approval the action waits for rather than who gets a notification afterward. If it cannot be undone, a human signs it.

“Which AI tools are your staff already using with company data today?”

Question five is the hard one, because the honest answer is usually “we do not know.”

In one tenant we reviewed, an AI assistant had been connected through a single staff member’s account almost two years earlier. It could read every OneDrive and SharePoint file that person could open, and it held that access without them signing in again. Nobody had approved it for the company. One person clicked accept on a permission screen, once, and it had been sitting there ever since.

That is not a discipline problem. That is what a permission screen is designed to do. But it means the review is not “what did we approve.” It is what is connected today, what can it reach, and which of those connections can act without anyone checking.

You cannot scope a new tool sensibly until you know what the old ones already hold.

Decide who can approve what. Announce your approval rules team wide.

Raise awareness across your team by publishing your AI use policies, and a framework for how to approach AI tool requests. Name the person(s) who can approve an AI tool on behalf of the company, and make sure anyone requesting a tool knows who it is. It is rarely the person asking.

Here at TUCU, Toronto Managed IT Services for small business and non profits, we do not install or configure an AI tool until a person with authority to accept the risk says so in writing. Not the person who requested it. Someone who can accept the obligation on behalf of the company. It sounds bureaucratic until the first time it stops something.

It is also worth asking your IT provider what their approval actually covers, because the answer is narrower than most owners assume. Ours covers one thing: the security posture of the application at the time we assessed it. It is not a statement that the tool is safe for your data, and it is not an assessment of whether the tool meets your privacy, legal, contractual or regulatory obligations.

And it says nothing about what the vendor ships next. That is the live risk right now. Vendors are adding agent features to tools that did not have them a year ago. An app approved when it could only read may be able to act after an update, on permissions you already granted and never revisited.

Where to start

Interview your staff. Answer the five questions. Find out what is already connected. Then set the rule about who approves what, and write it down before you choose a single new tool.

We help Toronto and Durham Region businesses work through holistic security for their business data. If you would like to lean on a reliable IT department to help you navigate ever changing cyberthreats and AI productivity tools, we can help. Learn more about TUCU and contact us today for a free consultation call about your IT and AI management needs.

Ready for a great Managed IT Provider?

Book a free discovery call to review your fully managed IT needs. If we’re a good fit, we’ll send you a tailored proposal and quote.

Book A Discovery Call

Tell us about your IT challenges. Let’s discuss how TUCU might help.