Protocol InstituteBusiness

Feed · thread · version 3 · updated 12 October 2026

Firms can rule each AI agent, not yet the whole fleet

The first report asked who owns an AI agent's rules. Its companion, What controls do AI agent products give firms, and how are they changing?, reads what agent products let firms control and how that has changed since 2021. It reads what vendors publish about their controls, as any buyer could, and dates when each kind of control first appeared.

From muzzles to handcuffs. The first AI controls were filters on speech: block a topic, mask a phone number, catch a jailbreak. Within about a year, new controls were mostly written for actions instead: which tools an agent may use, whose identity it carries, what it may spend, when a person must approve. Agents reached central policy over actions in about three years, faster than cloud or APIs did, likely in part by reusing the identity, gateway and policy machinery those systems had built.

But each handcuff fits one wrist. Plenty of rules are set once for the whole firm. When they are checked, nearly two times in three they still look at one action, one agent or one user. Only a small share of controls look across the whole firm, and most of those keep records or meter the vendor's bill. The analysis found just one that limits what agents do in total.

Why that matters. Picture ten thousand employees, each with well-governed agents. Every agent passes every check. Added up, small refund limits become a refund policy nobody wrote, and modest email caps become a mass mailing nobody approved. Trading learned this the hard way. In 2013 the SEC found that Knight Capital lacked controls able to stop orders beyond its capital limits "for the firm in the aggregate", and Europe now requires trading firms to hold firm-wide limits and a kill switch for all their orders. Agents have no equivalent yet.

The edge of the fleet. Every control reaches only as far as the firm owns: its devices, network and accounts. On the analysis's reading of the evidence, personal AI accounts and personal agents sit outside nearly all of them.

The report closes with twelve questions to ask vendors before scaling to thousands of agents. In short, the analysis suggests asking for controls over the fleet, not only over each agent. Both reports are on the Research page.

These are findings of an AI-assisted analysis of public sources. Its suggestions are not a consensus view of the research group or a position of the Protocol Institute.

Follow

Follow this blyg. Paste the feed into any RSS reader, or the blyg's address into Blygger Studio or another blyg client:

https://protocolsforbusiness.com/blyg/feed.xml

https://protocolsforbusiness.com/blyg/

To follow every member too, import blogroll.opml.

Join the conversation

This is a feed, not a forum. Two ways to answer a post:

  • Talk about it on Discord. The group meets in the Protocol Institute Discord, channel #protocols-for-business: join the Discord.
  • Respond from your own blyg. Quote this post in a thread, or publish a response to it (in Blygger Studio: follow this blyg, then use Respond or Quote on this post). Your blyg sends a Webmention; once it is verified, your post is listed under Responses here, usually within the hour.

    Blyg ID 7bfwg8vp4h7tjzpq3rvfrzmsa5

    Quote line ![[7bfwg8vp4h7tjzpq3rvfrzmsa5]]

    Respond to (stub_of) {"origin": "https://protocolsforbusiness.com/blyg/", "id": "7bfwg8vp4h7tjzpq3rvfrzmsa5", "version": 3}

    Webmention endpoint https://protocolsforbusiness.com/blyg/webmention

  • No blyg yet? Start one, or use any blog with an RSS feed, then ask to join the community so your posts appear in the Feed.

Machine-readable: item JSON · changelog 3 versions