Which critical vulnerabilities affect the most assets across our Tenable estate?
Tenable connects Memtro to Tenable Vulnerability Management. It reads vulnerabilities across your estate, most severe first, with VPR, CVSS and how many assets each affects. It reads assets with their exposure and criticality scores, one asset's vulnerabilities, and your scans with status, run history and findings by severity. Tags and scanners are there too. When asked and granted, it can launch, stop, pause, resume or delete a scan, create a tag, and add or remove tags on assets. Workbench reads are capped by Tenable at 5,000 rows and 450 days, and listing scanners needs the Scan Manager role.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Tenable tool, reads what it needs, and answers with the source cited.
These tools change something in Tenable. 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.
Once Tenable 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.
Tenable + MemtroWhich critical vulnerabilities affect the most assets?
Which assets have the highest exposure scores?
What did the latest run of the external scan find, by severity?
Which scanners are switched off?
Pause the weekly internal scan.
Maya Okafor, security lead at Acme Ltd, asked which critical vulnerabilities touched the most assets. Memtro listed the critical findings from the vulnerability workbench with their VPR and affected-asset counts, then the most exposed asset's other vulnerabilities. She took the list to the weekly patch review.
Tom Reilly, IT manager at Northwind, saw a scan slowing a busy network and asked Memtro to pause it. With the action granted to his team, Memtro paused the running scan and confirmed its status. That evening he asked it to resume the scan, and Tenable started sending scan traffic again.
The teams that lean on Tenable most, a question each of them asks, and what they connect beside it.
A record in Tenable 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
UpGuard
Uptime.com
Vanta
Zenduty
Cortex
WorkOS
Kandji
Automox
Huntress
SimpleMDM
Healthchecks.io
Rapid7 InsightVM
ZenhubIn Tenable, open the profile icon, then My Account, then API Keys, and generate a key pair. This replaces any pair you already had, and both keys are shown once.
In Memtro, open Connections → Tenable and paste the Access key and the Secret key.
An administrator grants the scan and tag actions by name to the teams that may use them. Listing scanners needs the Scan Manager role in Tenable.
Ask which critical vulnerabilities affect the most assets.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Tenable tools are the same everywhere.
Only when you ask, and only what it has been granted: launch a scan, optionally against other targets (scans the customer's network); stop a running scan; pause a running scan; resume a paused scan; delete a scan with its results (permanent); create a tag value in a category; add or remove tags on assets. 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.
Access key and secret key. In Tenable, open the profile icon, then My Account, then API Keys, and generate a key pair. This replaces any pair you already had, and both keys are shown once.
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
