Skip to main content
Glama

burp_stop

Stop Burp Suite instances during penetration testing to manage security assessment workflows and control exploitation processes.

Instructions

Stop Burp Suite instance

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler function that executes the burp_stop tool logic: kills the Burp Suite child process if running and returns a standardized ScanResult object.
    async stopBurpSuite(): Promise<ScanResult> {
      try {
        console.error('🛑 Stopping Burp Suite...');
    
        if (this.burpProcess) {
          this.burpProcess.kill('SIGTERM');
          this.burpProcess = null;
        }
    
        return {
          target: 'burpsuite',
          timestamp: new Date().toISOString(),
          tool: 'burpsuite_shutdown',
          results: {
            status: 'stopped'
          },
          status: 'success'
        };
    
      } catch (error) {
        return {
          target: 'burpsuite',
          timestamp: new Date().toISOString(),
          tool: 'burpsuite_shutdown',
          results: {},
          status: 'error',
          error: error instanceof Error ? error.message : String(error)
        };
      }
    }
  • src/index.ts:420-427 (registration)
    Registers the 'burp_stop' tool in the MCP server's listTools response, including its name, description, and empty input schema.
      name: "burp_stop",
      description: "Stop Burp Suite instance",
      inputSchema: {
        type: "object",
        properties: {},
        required: []
      }
    },
  • The dispatch handler in the main tool call switch statement that invokes the BurpSuiteIntegration.stopBurpSuite() method and formats the response.
    case "burp_stop":
      return respond(await this.burpSuite.stopBurpSuite());
  • The input schema definition for the burp_stop tool, specifying no required parameters.
    inputSchema: {
      type: "object",
      properties: {},
      required: []
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('stop') but doesn't describe what 'stop' entails—whether it gracefully shuts down the instance, terminates processes, affects other tools, or requires specific permissions. For a tool with zero annotation coverage, this lack of behavioral detail is a significant gap, though it doesn't contradict any annotations.

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—'Stop Burp Suite instance'—that is front-loaded with the core action. It wastes no words and is appropriately sized for a simple tool with no parameters. Every part of the sentence earns its place by specifying the verb and target.

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 tool's complexity (simple action with no parameters) and lack of annotations and output schema, the description is incomplete. It doesn't explain what 'stop' means behaviorally, what happens after stopping, or any dependencies (e.g., requires a running instance). For a tool that likely interacts with a security testing suite, more context on effects and prerequisites is needed.

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

Parameters4/5

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

The tool has 0 parameters, and schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics, and it appropriately avoids mentioning any. This meets the baseline expectation for a parameterless tool, though it doesn't go beyond that.

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 'Stop Burp Suite instance' clearly states the action (stop) and target resource (Burp Suite instance), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'burp_start', but the verb 'stop' inherently contrasts with 'start', providing some implicit distinction. The description avoids tautology by not merely restating the tool name.

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., that a Burp Suite instance must be running), exclusions, or relationships with sibling tools like 'burp_start'. While the action 'stop' implies it should be used after starting an instance, this is not explicitly stated, leaving usage context unclear.

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