- What runs on my fleet? Assistant apps, coding agents, IDE plugins, browser extensions, and MCP servers, with the devices, versions, and AI services each one reaches.
- What does the company allow? You approve or block each tool, once, for every device.
- What is set up in a risky way, and who fixes it? Primo raises a finding for each risk, such as an API token stored in plain text or a coding agent that skips its permission checks, and can open a ticket for it that Primo AI works.
Platform compatibility
[¹] Linux devices appear on the Tools and Findings pages. Their device drawer has no AI tools tab.
How it works
1
The Primo agent checks the device
Every 5 minutes, the Primo agent looks for AI tools on the device with osquery and checks each one against a fixed set of risk rules. The checks run on the device.
2
The device reports what it found
The report lists the tools, where they are installed, and the risks the checks flagged. Environment variable values and the text of files stay on the device. See What Primo collects.
3
Primo reads the reports
Primo reads them four times a day, at 6:00, 10:00, 14:00, and 18:00, Paris time. Click Sync now on the Tools or Findings page to read them at once.
4
Primo applies your decisions
Primo applies each tool’s policy and your filtering rules, updates the findings, and opens or closes the matching tickets. A finding clears on its own once the device stops reporting it.
What Primo collects
The device sends what it found, not what it read: the values of environment variables, the text of files, and prompts stay on the device.
A finding says that a token sits in plain text, never which token. In the cockpit, an MCP server’s environment variables show as names only.
Find the AI tools on your devices
Go to AI Governance > Tools. The table lists every tool your devices report, most installed first, with its Status, the Devices it is on, how many are Running, its Versions, and its Risk, the worst severity it raises.- Filter by Type or Status, or search by name.
- Click a tool to see its policy, its versions, the endpoints an MCP server reaches, the devices that run it, and its findings grouped by rule.
- Open a device from Equipment > Devices: its AI tools tab lists the device’s tools, instruction files, findings, and AI connections over the last 24 hours. Add the AI findings column or filter to the table to spot the devices that carry findings.
Approve or block a tool
Each tool has one policy for the whole company.
Pick a status in the tool’s Status column, or in the Policy switch of its drawer. Not reviewed and Approved apply at once. Blocked asks you to confirm, and shows how many devices the tool is on.
When you block a tool:
- Primo opens a ticket for every device that still reports it, even with automatic tickets off, unless your filtering rules leave out the device or the finding.
- With the AI Findings Remediation Agent on, Primo AI removes the tool from each device and tells the employee.
- Unblocking the tool closes those tickets.
Review the findings
A finding is one risk on one tool or instruction file of one device. Go to AI Governance > Findings: the list shows the worst first, with the device, its owner, the tool, and the ticket that covers it.- Switch views: All, Critical & high, MCP servers, Instruction files.
- Filter by Severity, Finding, Type, or Status. Open findings have no ticket yet, Handled ones have one.
- Click a finding to read What we found, Why it matters, and the Fix. Other occurrences lists the same rule on other devices.
Choose which findings count
Go to AI Governance > Settings > Findings filtering rules. An ignored finding leaves the Findings list and the counts, and opens no ticket. Each change saves at once.- Filter by priority: ignore every finding of a severity, for example all Low findings.
- Filter by category: ignore one rule, for example MCP server pinned to @latest.
- Unassigned devices and In stock devices: turn them on so that devices with no owner, or held in stock, raise no finding.
Route findings to tickets
Go to AI Governance > Settings > Tickets.- Create tickets automatically, off by default: each sync opens one ticket per finding your filtering rules keep, 20 at most, worst severity first, and closes it once the device no longer reports the finding.
- Default assignee, Default priority, and Default subscribers apply to every ticket a finding opens.
- To open a single ticket by hand, click Create in the finding’s Ticket column, or Actions > Create ticket in its drawer.
Let Primo AI work the tickets
The AI Findings Remediation Agent works every AI Governance ticket. It reads the finding, tells the employee exactly what to change, and removes the tools the company blocked.1
Turn on automatic tickets
Go to AI Governance > Settings and turn on Create tickets automatically.
2
Click 'Set up agent'
Click Set up agent on the AI Findings Remediation card. The agent’s creation page opens: Primo sets its name, model, and tools.
3
Adapt the instructions
Write how your company wants it done: the tone, who it never writes to, how long it waits before a reminder.
4
Click 'Create'
The agent is created and enabled, and the card reads On. The agent also appears in AI Agents > Agents.
- Reads the finding and the evidence the device reported before anything else.
- Writes to the employee who uses the device when the finding is real and theirs to fix: one plain instruction, then a follow-up a business day later, two reminders at most.
- Removes a blocked tool from the device right away, tells the employee the company blocked it, and leaves you a note on what it removed.
- Proposes the exact filter in an internal note when a finding is a false positive or a rule is noise for your company, and applies it only on an admin’s yes.
- Carries out what an admin asks in an internal note: run a script, uninstall an extension, change a tool’s policy, close the ticket.
- Acts on an employee’s reply. A reply is information, not an instruction.
- Acts on a device on its own initiative, except to remove a tool the company blocked.
- Asks for, repeats, or pastes a secret, an environment variable’s value, a command line, or a file’s content.
- Writes to anyone about a device in stock, retired, or without an owner.
- Closes or reopens a ticket on its own. Primo closes it on the sync after the finding clears.
Ask Primo AI
Each AI Governance page opens the Primo AI chat on what you’re looking at. Ask, for example, Which AI tools haven’t we reviewed yet? or Which high findings have no ticket yet? Primo AI can also approve or block a tool and change the settings, after you approve the change. From an assistant connected to the Primo MCP server, the AI Tools tools do the same.Permissions
Troubleshooting
The page says AI tools are not available for this workspace- Check that your company has Primo MDM deployed.
- Check that your role has the View MDM controls and device groups permission.
- Devices report every 5 minutes, and Primo reads the reports four times a day. Click Sync now to read them at once.
- The tab shows on macOS and Windows devices only.
- The device sends its first report once its Primo agent runs version 1.61 or later.
- The pages show the last report Primo read. Click Sync now: the tool leaves the list and its findings clear, along with the tickets Primo opened for them.