Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

Tenable Vulnerability Management (BYOK) — connector documentation

  • MCP endpoint: https://byok-tenable.connectorbay.com/mcp
  • REST API: POST https://byok-tenable.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-tenable.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Tenable Vulnerability Management Tenable API keys as one string: accessKey=ACCESS_KEY;secretKey=SECRET_KEY, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-tenable.connectorbay.com/health · Tool schemas: https://byok-tenable.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-tenable · agent@connectorbay.com

What Tenable Vulnerability Management (BYOK) is for

Tenable Vulnerability Management (BYOK) lets an AI assistant read your own Tenable Vulnerability Management data through the Tenable Vulnerability Management API with a key you supply (Tenable API keys as one string: accessKey=ACCESS_KEY;secretKey=SECRET_KEY). Read-only: 12 tools (list_scans, get_scan, get_scan_history, get_scan_status, list_assets, get_asset, list_vulnerabilities, list_asset_vulnerabilities, get_vulnerability_details, get_plugin, list_folders, list_policies). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to cloud.tenable.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Tenable Vulnerability Management. Tenable Vulnerability Management and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which Tenable scans are running or failed recently?"
  • "What did Tenable scan 42 find?"
  • "When did Tenable scan 42 run before?"
  • "Is Tenable scan 42 finished?"
  • "Which assets does Tenable know about?"
  • "Show me Tenable asset details for a UUID"

What it does

  • list_scans: List scan configurations you can view, with status, owner, last start time, progress and schedule details.
  • get_scan: Get the results of one scan (latest run, or a past run via history_id): scan info, host list with severity counts, and vulnerabilities found.
  • get_scan_history: List the past runs of one scan with status, start and end times and whether results are archived.
  • get_scan_status: Get only the latest status of one scan (for example running, completed, canceled).
  • list_assets: List assets Tenable has identified, with IP addresses, FQDNs, operating systems, last seen time, ACR and exposure scores and sources. May hold up to 5,000 assets; the answer is trimmed.
  • get_asset: Get one asset by UUID: names, addresses, operating system, tags, installed software, scores and first and last seen times.
  • list_vulnerabilities: List recorded vulnerabilities across all assets (grouped by plugin) with severity, VPR score, CVSS scores, and how many times each was found. Severity 0 is info and 4 is critical.
  • list_asset_vulnerabilities: List the vulnerabilities recorded on one asset, with severity, VPR score, CVSS scores and state.
  • get_vulnerability_details: Get the details of one vulnerability plugin: description, synopsis, solution, severity, VPR, CVSS vectors, exploit availability and references.
  • get_plugin: Get a Tenable plugin by id: its name, family, VPR score and attribute list.
  • list_folders: List the scan folders (Tenable-provided and custom) with type and unread count.
  • list_policies: List scan policies (templates) with owner, sharing state and creation and modification times.

BYOK key

You bring your own Tenable Vulnerability Management Tenable API keys as one string: accessKey=ACCESS_KEY;secretKey=SECRET_KEY (https://developer.tenable.com/docs/api-key-management). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to cloud.tenable.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the Tenable Vulnerability Management API (cloud.tenable.com) with a BYOK key; documentation: https://developer.tenable.com/reference/vulnerability-management. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Tenable Vulnerability Management. Tenable Vulnerability Management and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Tenable Vulnerability Management account.

Built for: Worldwide. Languages: English.