Which devices are missing critical patches, and which need a reboot?
Automox connects Memtro to your endpoint patching. It reads devices with OS, agent, compliance, pending patches and next patch window, a device's missing patches with severity and CVEs, policies with their compliance counts, devices needing attention, the event log, manual approvals and device groups. When asked, and once an administrator has granted the action by name, it can scan a device, reboot it, install named patches or all updates, run a policy on one device, approve or reject a patch, and move, rename or mark a device as an exception. IP addresses, serial numbers and logged-in users are never returned.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Automox tool, reads what it needs, and answers with the source cited.
These tools change something in Automox. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Automox for you. Each event can start a job, with the event as its input. Automox signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Automox is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
Automox + MemtroWhich devices are missing critical patches?
Which machines need a reboot?
How compliant is the Windows workstations policy?
Which patches are waiting for approval?
Scan the finance laptop FIN-LT-07 now
Tom Reilly, IT manager at Acme Ltd, asked which devices needed attention. Memtro listed the non-compliant counts by severity and named the devices with critical patches missing, noting which were offline and which needed a reboot.
Priya Sharma, systems administrator at Northwind, asked Memtro to approve the browser update waiting for manual approval. Memtro approved it in Automox, which released it to every device under that policy at the next run.
The teams that lean on Automox most, a question each of them asks, and what they connect beside it.
A record in Automox is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
UptimeRobot
Honeycomb
Cronitor
FireHydrant
StatusCake
GlitchTip
GLPI
Langfuse
LibreNMS
NetBox
Snipe-IT
Woodpecker CI
Zabbix
LangSmith
Helicone
GrowthBook
Drata
Intruder
GitGuardian
Secureframe
ilert
JumpCloud
ConfigCat
Split
Aikido Security
Astronomer
Comet Opik
CrowdStrike Falcon
Detectify
Domotz
LambdaTest
LangWatch
LlamaCloud
Logz.io
Lunary
NinjaOne
Northflank
Portkey
PromptLayer
PRTG Network Monitor
Raygun
Retell AI
Runpod
Shodan
Spike.sh
Squadcast
Tenable
UpGuard
Uptime.com
Vanta
Zenduty
Cortex
WorkOS
Kandji
Huntress
SimpleMDM
Healthchecks.io
Rapid7 InsightVM
ZenhubIn the Automox console, open Settings → Keys and create a key for a dedicated user. The key acts with its user's permissions, so make that user read-only unless Memtro should act.
Copy the key, and note your numeric organisation id from the console URL.
In Memtro, open Connections → Automox and paste them into API key and Organisation ID.
Ask your first question: which devices are missing critical patches?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Automox tools are the same everywhere.
Only when you ask, and only what it has been granted: scan a device now (refreshes its inventory and patch list); reboot a device now (interrupts whoever is using it); install named patches on a device now; install all available updates on a device now (ignores policy filters); run a policy now on one device; approve or reject a patch waiting for manual approval; move a device to another group, rename it, or mark it an exception. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
API key and Organisation ID. In the Automox console, open Settings → Keys and create a key for a dedicated user. The key acts with its user's permissions, so make that user read-only unless Memtro should act.
Yes. Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Automox for you. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time
