Skip to main content
Glama

burp_proxy_scan

Perform passive security scanning by proxying web traffic through Burp Suite to identify vulnerabilities during authorized penetration testing.

Instructions

Perform passive scan through Burp Suite proxy

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetYesTarget URL to proxy through
durationNoScan duration in seconds (default: 300)

Implementation Reference

  • The main handler function that executes the burp_proxy_scan tool logic. It checks Burp status, generates proxy traffic to the target, retrieves proxy history and passive scan issues.
    async proxyScan(target: string, duration: number = 300): Promise<ScanResult> {
      try {
        console.error(`🔍 Starting Burp Suite proxy scan on ${target} for ${duration} seconds`);
    
        // Check if Burp is running
        await this.checkBurpStatus();
    
        // Configure proxy
        const proxyConfig = {
          http_proxy: `http://127.0.0.1:${this.config.proxy_port}`,
          https_proxy: `http://127.0.0.1:${this.config.proxy_port}`
        };
    
        // Send some requests through proxy to generate traffic
        await this.generateProxyTraffic(target, duration);
    
        // Get proxy history
        const proxyHistory = await this.getProxyHistory();
    
        // Get passive scan issues
        const issues = await this.getPassiveIssues();
    
        return {
          target,
          timestamp: new Date().toISOString(),
          tool: 'burpsuite_proxy_scan',
          results: {
            proxy_config: proxyConfig,
            scan_duration: duration,
            requests_captured: proxyHistory.length,
            issue_count: issues.length,
            issues: issues,
            proxy_history: proxyHistory.slice(0, 50), // Limit output
            severity_breakdown: this.categorizeBySeverity(issues)
          },
          status: 'success'
        };
    
      } catch (error) {
        return {
          target,
          timestamp: new Date().toISOString(),
          tool: 'burpsuite_proxy_scan',
          results: {},
          status: 'error',
          error: error instanceof Error ? error.message : String(error)
        };
      }
    }
  • Input schema definition for the burp_proxy_scan tool, specifying target URL and optional duration.
    {
      name: "burp_proxy_scan",
      description: "Perform passive scan through Burp Suite proxy",
      inputSchema: {
        type: "object",
        properties: {
          target: { type: "string", description: "Target URL to proxy through" },
          duration: { type: "number", description: "Scan duration in seconds (default: 300)" }
        },
        required: ["target"]
      }
    },
  • src/index.ts:601-603 (registration)
    Tool registration in the switch statement of the CallToolRequestSchema handler, delegating to BurpSuiteIntegration.proxyScan method.
    case "burp_proxy_scan":
      return respond(await this.burpSuite.proxyScan(args.target, args.duration || 300));
  • src/index.ts:444-455 (registration)
    Tool registration in the ListToolsRequestSchema response array.
    {
      name: "burp_proxy_scan",
      description: "Perform passive scan through Burp Suite proxy",
      inputSchema: {
        type: "object",
        properties: {
          target: { type: "string", description: "Target URL to proxy through" },
          duration: { type: "number", description: "Scan duration in seconds (default: 300)" }
        },
        required: ["target"]
      }
    },
  • Helper function to generate proxy traffic by sending curl requests through Burp proxy.
    private async generateProxyTraffic(target: string, duration: number): Promise<void> {
      // Use curl or similar tool to generate traffic through Burp proxy
      const proxyUrl = `http://127.0.0.1:${this.config.proxy_port}`;
      
      try {
        // Basic crawling through proxy
        const command = `curl -x ${proxyUrl} -k -s "${target}" > /dev/null`;
        await execAsync(command, { timeout: duration * 1000 });
      } catch (error) {
        console.error('Error generating proxy traffic:', error);
      }
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'passive scan' which suggests non-intrusive monitoring, but fails to detail critical aspects like required permissions, impact on the target, rate limits, or what the scan entails operationally (e.g., traffic analysis vs. vulnerability detection).

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 appropriately sized and front-loaded, with every word contributing to understanding the core functionality.

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 security scanning tools, no annotations, and no output schema, the description is insufficient. It lacks details on what the scan does (e.g., types of vulnerabilities detected), output format, error handling, or integration with other tools like 'burp_export' or 'generate_report'.

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%, so the schema fully documents the two parameters (target URL and duration). The description adds no additional parameter semantics beyond what the schema provides, such as format examples or constraints, meeting the baseline for high coverage.

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 ('perform passive scan') and the mechanism ('through Burp Suite proxy'), which distinguishes it from active scanning tools. However, it doesn't explicitly differentiate from sibling tools like 'burp_active_scan' or 'burp_spider' beyond the 'passive' qualifier.

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 explicit guidance on when to use this tool versus alternatives like 'burp_active_scan' or 'burp_spider' is provided. The description implies a passive scanning context but lacks details on prerequisites, scenarios, or exclusions for usage.

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

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/adriyansyah-mf/mcp-pentest'

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