Skip to main content
Glama

get_proxy_history

Retrieve captured HTTP/HTTPS traffic from Burp Proxy, filter by host, method, or status code, and limit results for targeted analysis.

Instructions

Get HTTP/HTTPS traffic captured by Burp Proxy

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostNoFilter by host (optional)
limitNoMaximum number of items to return (default: 10)
methodNoFilter by HTTP method (optional)
status_codeNoFilter by HTTP status code (optional)

Implementation Reference

  • The handler for the 'get_proxy_history' tool. It extracts optional filter parameters (host, method, status_code, limit) from the arguments, filters the mockProxyHistory array accordingly, and returns a JSON-formatted text content with summary of matching items including id, host, method, url, status_code, time, size, and mime_type.
    case "get_proxy_history": {
      const host = request.params.arguments?.host as string | undefined;
      const method = request.params.arguments?.method as string | undefined;
      const statusCode = request.params.arguments?.status_code as number | undefined;
      const limit = Number(request.params.arguments?.limit || 10);
    
      let history = [...mockProxyHistory];
    
      // Apply filters
      if (host) {
        history = history.filter(item => item.host.includes(host));
      }
    
      if (method) {
        history = history.filter(item => item.method === method.toUpperCase());
      }
    
      if (statusCode) {
        history = history.filter(item => item.statusCode === statusCode);
      }
    
      // Apply limit
      history = history.slice(0, limit);
    
      return {
        content: [{
          type: "text",
          text: JSON.stringify({
            total_items: history.length,
            items: history.map(item => ({
              id: item.id,
              host: item.host,
              method: item.method,
              url: item.url,
              status_code: item.statusCode,
              time: item.time,
              size: item.size,
              mime_type: item.mimeType
            }))
          }, null, 2)
        }]
      };
    }
  • src/index.ts:435-458 (registration)
    Registration of the 'get_proxy_history' tool in the ListToolsRequestSchema handler, including its name, description, and inputSchema defining optional parameters for filtering proxy history.
      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)"
          }
        }
      }
    },
  • TypeScript interface defining the structure of ProxyHistoryItem, used for typing the mock data and implicitly the tool's data handling.
    interface ProxyHistoryItem {
      id: string;
      host: string;
      method: string;
      url: string;
      statusCode: number;
      request: string;
      response: string;
      time: string;
      size: number;
      mimeType: string;
    }
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 states what the tool does but lacks details on permissions needed, rate limits, whether it returns real-time or historical data, or the format of the returned traffic. For a tool that retrieves potentially sensitive proxy data, this is a significant gap in transparency.

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 with zero wasted words. It's appropriately sized and front-loaded, making it easy to understand at a glance.

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 retrieving proxy traffic (which could involve large datasets or sensitive information), no annotations, and no output schema, the description is incomplete. It doesn't explain what the returned data looks like, any limitations, or how it integrates with the sibling tools, leaving gaps for an AI agent to use it effectively.

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 schema description coverage is 100%, with clear descriptions for all four parameters (host, limit, method, status_code). The description adds no additional parameter semantics beyond what the schema provides, so it meets the baseline score of 3 without compensating for any gaps.

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 ('HTTP/HTTPS traffic captured by Burp Proxy'), making the tool's purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get_site_map' or 'get_scan_issues', which might also retrieve related data, so it doesn't reach the highest 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 any prerequisites, context for filtering traffic, or how it differs from siblings like 'get_site_map' (which might retrieve site structure) or 'get_scan_issues' (which might retrieve security findings).

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