tenable-mcp

tenable_list_findings

Read-only

List vulnerability findings from Tenable with filters for severity, state, CVE, exploit availability, and more. Retrieve current vulnerabilities across your environment.

Instructions

List vulnerability findings using the Tenable exports API.

Uses the modern exports.vulns() API for the most current view of vulnerabilities across your environment.

Example: Input: {"severity": "high", "state": "OPEN", "limit": 100} Output: {"findings": [...], "total": 45}

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_findings"
  }
}

Input Schema

Name	Required	Description	Default
`cve`	No
`tags`	No
`limit`	No
`since`	No
`state`	No
`severity`	No
`plugin_id`	No
`exploit_available`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 9, 2026

TDQS

C2.9/5.0

Behavior3/5

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

The readOnlyHint annotation indicates a safe read operation, which the description's 'list' verb aligns with. The description adds the API method name (exports.vulns()) but does not disclose additional behavioral traits like data freshness, pagination, or rate limits.

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

Conciseness4/5

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

The description is concise (two sentences plus an example) and front-loaded with the key action. Every sentence adds value, though the example could be considered part of the description.

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

Completeness2/5

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

Given 8 parameters and no output schema, the description is too brief. It lacks explanations of filtering, pagination, return structure beyond the partial example, and how to interpret results. The context signals indicate high complexity that the description does not address.

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

Parameters2/5

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

No parameter descriptions are provided in the text. The example hints at severity, state, and limit, but with 0% schema coverage, the description fails to explain the meaning, valid values, or effect of the 8 parameters beyond their names and types.

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

Purpose4/5

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

Description clearly states the tool lists vulnerability findings using the Tenable exports API. It includes an example and mentions the modern API. However, it does not explicitly differentiate from sibling tools like tenable_get_vulnerability_details or tenable_search_vulnerabilities, which could overlap in purpose.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. The description does not mention when it is appropriate to use, when not to use, or any prerequisites.

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

Deploy Server