Skip to main content
Glama
Cyreslab-AI

Nessus MCP Server

get_vulnerability_details

Retrieve comprehensive details about a specific vulnerability by providing its unique ID, such as CVE identifiers, using the Nessus MCP Server for advanced security insights.

Instructions

Get detailed information about a specific vulnerability

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vulnerability_idYesID of the vulnerability (e.g., CVE-2021-44228)

Implementation Reference

  • The primary handler function that executes the get_vulnerability_details tool logic, including input validation, API call to fetch details, formatting, and error handling.
    export const getVulnerabilityDetailsToolHandler = async (args: Record<string, unknown>) => {
      try {
        // Validate arguments
        const vulnId = validateVulnerabilityId(args.vulnerability_id);
    
        // Get vulnerability details
        const details = await getVulnerabilityDetails(vulnId);
    
        // Check if there was an error
        if ('error' in details) {
          return {
            content: [
              {
                type: 'text',
                text: `Error: ${details.error}`
              }
            ],
            isError: true
          };
        }
    
        // Format the vulnerability details
        const formattedDetails = formatVulnerabilityDetails(details);
    
        return {
          content: [
            {
              type: 'text',
              text: formattedDetails
            }
          ]
        };
      } catch (error) {
        const mcpError = handleNessusApiError(error);
        return {
          content: [
            {
              type: 'text',
              text: `Error: ${mcpError.message}`
            }
          ],
          isError: true
        };
      }
    };
  • Defines the input schema and metadata for the get_vulnerability_details tool.
    export const getVulnerabilityDetailsToolSchema = {
      name: 'get_vulnerability_details',
      description: 'Get detailed information about a specific vulnerability',
      inputSchema: {
        type: 'object',
        properties: {
          vulnerability_id: {
            type: 'string',
            description: 'ID of the vulnerability (e.g., CVE-2021-44228)'
          }
        },
        required: ['vulnerability_id']
      }
    };
  • src/index.ts:107-108 (registration)
    Registers and dispatches the get_vulnerability_details tool handler in the main CallToolRequestSchema switch statement.
    case 'get_vulnerability_details':
      return await getVulnerabilityDetailsToolHandler(args);
  • src/index.ts:71-86 (registration)
    Registers the tool schema in the ListToolsRequestSchema handler, making it discoverable.
    server.setRequestHandler(
      ListToolsRequestSchema,
      async () => {
        return {
          tools: [
            listScanTemplatesToolSchema,
            startScanToolSchema,
            getScanStatusToolSchema,
            getScanResultsToolSchema,
            listScansToolSchema,
            getVulnerabilityDetailsToolSchema,
            searchVulnerabilitiesToolSchema
          ]
        };
      }
    );
  • Supporting function called by the handler to retrieve raw vulnerability details from mock data or real Nessus API.
    export const getVulnerabilityDetails = async (vulnId: string) => {
      if (config.useMock) {
        return getMockVulnerabilityDetails(vulnId);
      }
    
      // Real API implementation would go here
      throw new Error("Real API not implemented");
    };
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It states the tool retrieves 'detailed information' but doesn't specify what details are included, whether it's a read-only operation, if authentication is required, or any rate limits. The description is too vague to inform the agent about operational traits beyond the basic purpose.

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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It is front-loaded with the core action and resource, making it easy to parse quickly. Every part of the sentence earns its place by conveying essential information.

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 the complexity of vulnerability details (which could include technical data, severity scores, patches, etc.), no annotations, and no output schema, the description is insufficient. It doesn't hint at the type or structure of information returned, leaving the agent unprepared for what to expect from the tool's output.

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?

Schema description coverage is 100%, with the parameter 'vulnerability_id' clearly documented in the schema as 'ID of the vulnerability (e.g., CVE-2021-44228)'. The description adds no additional parameter semantics beyond what the schema provides, so it meets the baseline for high schema coverage without compensating value.

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?

The description clearly states the action ('Get detailed information') and target resource ('about a specific vulnerability'), making the purpose immediately understandable. It distinguishes from siblings like 'search_vulnerabilities' (which likely searches multiple) and 'get_scan_results' (which focuses on scan outputs). However, it doesn't explicitly contrast with siblings, keeping it from a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a vulnerability ID from another source), exclusions (e.g., not for bulk lookups), or direct comparisons to siblings like 'search_vulnerabilities' for broader queries. Usage is implied but not articulated.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Cyreslab-AI/nessus-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server