Skip to main content
Glama

get_scan_issues

Retrieve vulnerability issues from a scan by specifying the scan ID and filtering by severity levels, including high, medium, low, and info, for detailed analysis and action.

Instructions

Get vulnerability issues found in a scan

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scan_idYesID of the scan
severityNoFilter issues by severity

Implementation Reference

  • Handler function that executes the 'get_scan_issues' tool. Retrieves issues from a scan by ID, filters by optional severity, and returns a summarized JSON response with issue details.
    case "get_scan_issues": {
      const scanId = String(request.params.arguments?.scan_id);
      const severity = String(request.params.arguments?.severity || "all");
    
      if (!scanId || !mockScans[scanId]) {
        throw new McpError(ErrorCode.InvalidRequest, `Scan ${scanId} not found`);
      }
    
      const scan = mockScans[scanId];
      let issues = scan.issues;
    
      // Filter by severity if specified
      if (severity !== "all") {
        issues = issues.filter(issue => issue.severity === severity);
      }
    
      return {
        content: [{
          type: "text",
          text: JSON.stringify({
            scan_id: scanId,
            target: scan.target,
            issue_count: issues.length,
            issues: issues.map(issue => ({
              id: issue.id,
              name: issue.name,
              severity: issue.severity,
              confidence: issue.confidence,
              host: issue.host,
              path: issue.path
            }))
          }, null, 2)
        }]
      };
    }
  • Input schema definition for the 'get_scan_issues' tool, specifying required scan_id and optional severity filter.
    name: "get_scan_issues",
    description: "Get vulnerability issues found in a scan",
    inputSchema: {
      type: "object",
      properties: {
        scan_id: {
          type: "string",
          description: "ID of the scan"
        },
        severity: {
          type: "string",
          enum: ["high", "medium", "low", "info", "all"],
          description: "Filter issues by severity"
        }
      },
      required: ["scan_id"]
    }
  • src/index.ts:380-480 (registration)
    The tool is registered in the listTools response within the server's tool list, including this tool alongside others like start_scan.
    return {
      tools: [
        {
          name: "start_scan",
          description: "Start a new vulnerability scan on a target URL",
          inputSchema: {
            type: "object",
            properties: {
              target: {
                type: "string",
                description: "Target URL to scan (e.g., https://example.com)"
              },
              scan_type: {
                type: "string",
                enum: ["passive", "active", "full"],
                description: "Type of scan to perform"
              }
            },
            required: ["target"]
          }
        },
        {
          name: "get_scan_status",
          description: "Check the status of a running scan",
          inputSchema: {
            type: "object",
            properties: {
              scan_id: {
                type: "string",
                description: "ID of the scan to check"
              }
            },
            required: ["scan_id"]
          }
        },
        {
          name: "get_scan_issues",
          description: "Get vulnerability issues found in a scan",
          inputSchema: {
            type: "object",
            properties: {
              scan_id: {
                type: "string",
                description: "ID of the scan"
              },
              severity: {
                type: "string",
                enum: ["high", "medium", "low", "info", "all"],
                description: "Filter issues by severity"
              }
            },
            required: ["scan_id"]
          }
        },
        {
          name: "get_proxy_history",
          description: "Get HTTP/HTTPS traffic captured by Burp Proxy",
          inputSchema: {
            type: "object",
            properties: {
              host: {
                type: "string",
                description: "Filter by host (optional)"
              },
              method: {
                type: "string",
                description: "Filter by HTTP method (optional)"
              },
              status_code: {
                type: "number",
                description: "Filter by HTTP status code (optional)"
              },
              limit: {
                type: "number",
                description: "Maximum number of items to return (default: 10)"
              }
            }
          }
        },
        {
          name: "get_site_map",
          description: "Get the site structure discovered during scanning and browsing",
          inputSchema: {
            type: "object",
            properties: {
              host: {
                type: "string",
                description: "Filter by host (optional)"
              },
              with_parameters: {
                type: "boolean",
                description: "Only show URLs with parameters (optional)"
              },
              limit: {
                type: "number",
                description: "Maximum number of items to return (default: 20)"
              }
            }
          }
        }
      ]
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 only states what the tool does without behavioral details. It lacks information on permissions, rate limits, pagination, or what happens if the scan_id is invalid, which is critical for a tool accessing vulnerability data.

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 function without unnecessary words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 scanning, lack of annotations, and no output schema, the description is insufficient. It doesn't explain return values, error handling, or behavioral constraints, leaving gaps that could hinder correct tool invocation by an agent.

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 mentions 'vulnerability issues' and 'scan', which aligns with the 'scan_id' parameter, but adds no meaning beyond the schema's 100% coverage. Since the schema fully describes both parameters, the baseline score of 3 is appropriate as the description doesn't enhance parameter understanding.

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') and resource ('vulnerability issues found in a scan'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'get_scan_status' or 'get_proxy_history', which prevents 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?

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't clarify if this should be used after 'start_scan' or alongside 'get_scan_status', leaving the agent without context for selection among siblings.

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/burpsuite-mcp-server'

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