DEVICE NOTE · 2026-10-10
AI usage control: what the term means for buyers
A new market name tends to arrive before buyers agree on what it includes. Here is how it maps onto the finder's control types.
Short answer
By The Device Desk · Endpoint AI Finder · Published 2026-10-10 · 4 min read
Desk research from public vendor pages read on 27 September and 11 October 2026. Profiles follow our published method; we did not run the products.
Where does the term come from?
Analyst firms name markets so they can compare vendors. In August 2026 Harmonic Security published a summary of a Gartner Market Overview for AI Usage Control, quoting Gartner's prediction that "by 2030, more than half of enterprises will use dedicated AI usage control technologies." We have not read the Gartner report itself, which is subscriber research; what we know of it here is what Harmonic Security reports. Lasso Security also uses the phrase for one of its product pages, AI usage control, which describes a browser extension and proxy integrations.
What does AI usage control usually cover?
The common core is employee use of AI tools: which tools are in use, which are approved, what data goes into them, and what happens when someone tries to share something sensitive. That is mostly the browser and the network, the positions where chat tools and their traffic can be seen.
Vendors stretch the term in different directions. Harmonic Security's product covers browser extensions, desktop apps and CLI tools, MCP gateways and an API, with block, warn or log. Lasso Security's AI usage control page describes a browser extension and proxy integrations. Other vendors in this site's set use different words for overlapping things: Onyx Security calls itself a secure AI control plane, and Bay calls itself an agentic security platform for endpoints.
How does it map to the five control types?
- Browser extension: the centre of most AI usage control products.
- Network or SSE proxy: common, especially where companies already route traffic through one.
- AI or MCP gateway: increasingly included, as agents call tools.
- On-device control: sometimes, usually for desktop apps and CLI tools rather than deep agent control.
- Policy only: the starting point the products enforce.
The finder does not use the term, because it does not tell you where a product sits. Two products both sold as AI usage control can cover different positions, and the positions decide what each can see.
What should you ask a vendor who uses the term?
- Which positions does your product cover: browser, network, gateway, device?
- Does it see coding agents and MCP servers on the device, or only AI services on the web?
- Can it warn or mask, or only block?
- How does it decide what data is sensitive?
- What does it record, and can the record tell a person from an agent?
What do the vendors in this set call themselves?
The names vary more than the products. Among the products we cover, Harmonic Security frames its product around data protection in everyday AI use, Lasso Security uses AI usage control for one product page, Onyx Security uses secure AI control plane, Noma Security lists AI-SPM, Agent Access Control and AI detection and response, and Bay describes a preventive agentic security platform for endpoints. A buyer comparing them should translate each name into positions and actions before comparing anything else.
Does a company need a dedicated AI usage control product?
Not always. The prediction Harmonic Security quotes is about dedicated products over the next few years, not a requirement for every company now. A company with a handful of AI users and general information may do well with a policy and the settings its tools already have, and the finder will say so. A company with broad browser AI use and customer data in reach will usually want something in the browser or on the network path. A company with coding agents will want something on the device as well.
Why does the name matter at all?
Because procurement often starts from a category. If a request for proposal asks for AI usage control, check that the requirements name the positions and actions you need, not only the category, so a browser-only product and a device-focused one are not compared as if they did the same job.
How do we use the term on this site?
Only when a vendor or a source uses it, and with the source shown. Our own structure stays with the five control types, because they describe where a control sits and therefore what it can see. If you arrive here searching for AI usage control, the browser extension and network or SSE proxy guides are the closest match, and the finder will tell you whether your situation calls for something in those positions, somewhere else, or nothing yet.
Sources
Source: Harmonic Security: Gartner AI usage control research · Read 27 Sep 2026
Source: Harmonic Security homepage · Read 27 Sep 2026
Source: Lasso Security: AI usage control · Read 27 Sep 2026
Source: Onyx Security homepage · Read 27 Sep 2026
Source: Noma Security homepage · Read 27 Sep 2026
Source: Bay homepage · Read 27 Sep 2026