tenable-mcp

tenable_list_assets

Read-only

Retrieve a paginated list of security assets with filters for hostname, IP address, tracking method, or network to identify inventory in Tenable Vulnerability Management.

Instructions

List assets from Tenable Vulnerability Management.

Returns a paginated list of assets with optional filters for hostname, IP address, tracking method, and network.

Example: Input: {"hostname": "web-server", "limit": 10} Output: {"assets": [...], "total": 10}

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tenable_list_assets"
  }
}

Input Schema

Name	Required	Description	Default
`ipv4`	No
`ipv6`	No
`limit`	No
`hostname`	No
`network_id`	No
`tracking_method`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 9, 2026

TDQS

A3.9/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description correctly identifies the tool as read-only (consistent with readOnlyHint annotation) and mentions pagination. However, it does not detail pagination behavior (e.g., default limit, max limit) or error handling, which would add value beyond the annotation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise with three clear sentences and a helpful example. Every sentence adds value without redundancy. It is well-structured for quick comprehension.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given six parameters, no schema descriptions, and no output schema, the description is adequate but incomplete. It provides an example and mentions filters but lacks details on parameter formats, valid values for tracking_method or network_id, and the structure of the response beyond a basic example.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description partially explains parameters by listing hostname, IP address, tracking method, and network as filters. However, it does not describe all six parameters (e.g., ipv4 vs ipv6 are not distinguished, limit is only implied in example). With 0% schema description coverage, the description should compensate more fully.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool lists assets from Tenable Vulnerability Management, with a specific verb and resource. It distinguishes from siblings like tenable_get_asset (single asset) and tenable_list_scans by focusing on assets. The mention of optional filters further clarifies its scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides context for usage: listing assets with optional filters and pagination. An example is given. However, it does not explicitly state when to use this tool vs alternatives like tenable_get_asset (for a single asset) or tenable_search_vulnerabilities.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server