Explainer

Every step was allowed. The sequence was the problem.

When a person works through an agent, each action can be permitted on its own and still add up to data leaving the company. Catching it means judging the run, not the call.

By the NoFly team

A run made of harmless steps

Picture an analyst working with an agent over one afternoon. None of these requests breaks a rule on its own.

  1. 01

    Query the customer table for the accounts that churned last quarter.

  2. 02

    Save the result as a file in the project folder.

  3. 03

    Shorten the file so it fits in a single message.

  4. 04

    Paste it into a personal notes app through an MCP server.

  5. 05

    Clear the project folder.

The sequence is illustrative. Every step is something people do every week. Together they describe customer data leaving through a personal account.

Why per-call rules miss it

A rule that looks at one call at a time sees a query, a file write, an edit, a paste and a delete. Blocking any of them stops real work. Allowing all of them without context lets the data walk out. The signal is in the order, and in where the data ended up.

What to look at instead

  • Where each piece of data was first read, and every place it was sent afterwards.
  • Whether the destination is a company system or a personal account.
  • Whether the run looks like this agent’s normal work, or like a first.
  • Who asked for each step, and whether the request came from the person or from something the agent read.

How NoFly helps

  • Protect

    Each run is kept as one connected record, and sensitive data is followed from the query that read it to the place it was sent, across tools and sub-agents. A new destination or kind of data raises a flag the first time it happens.

  • Discover

    Personal and company accounts are told apart for AI tools, so a paste into a personal workspace shows up as exactly that.

  • Govern

    An incident pulls the runs, calls and people involved into one case, so the investigation starts from the whole sequence.

What to do this week

This week3 actions
  1. Pick one agent and read a full day of its runs end to end, not call by call.
  2. List the places your agents can send data, and mark which of them are personal.
  3. Decide which data should never leave through an agent, and write it down as a rule.
Keep reading

More from the blog.

Find out what your AI is allowed to do today.

Book a call and we will map your agents, MCP servers and keys with you, or start on one laptop with the free scan.

Book a demo
npm i -g @nofly/agent