> For the complete documentation index, see [llms.txt](https://burp-ai-agent.six2dez.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://burp-ai-agent.six2dez.com/mcp-server/issue-create.md).

# Issue Creation (MCP)

The `issue_create` MCP tool lets an AI client create Burp issues programmatically.

## Tool Details

| Property            | Value                                                             |
| ------------------- | ----------------------------------------------------------------- |
| **Tool name**       | `issue_create`                                                    |
| **Category**        | Issues                                                            |
| **Native**          | Yes (registered in both the BApp Store and the GitHub full build) |
| **Unsafe**          | No                                                                |
| **Default enabled** | Yes                                                               |
| **Pro only**        | No                                                                |

## Workflow Sequence

```mermaid
sequenceDiagram
    participant User as Operator
    participant Client as MCP Client
    participant MCP as Burp MCP Server
    participant Burp as Burp Issue API

    User->>Client: Confirm finding and request issue creation
    Client->>MCP: issue_create(name, detail, severity, confidence, baseUrl, ...)
    MCP->>MCP: Validate input and sanitize text fields
    MCP->>Burp: Create issue with optional request/response attachments
    Burp-->>MCP: Issue created or validation error
    MCP-->>Client: Result payload
    Client-->>User: Confirmation and issue reference
```

## Input Parameters

| Parameter               | Type    | Required | Description                                                    |
| ----------------------- | ------- | -------- | -------------------------------------------------------------- |
| `name`                  | String  | Yes      | Issue title (for example, `SQL Injection in login parameter`). |
| `detail`                | String  | Yes      | Full evidence and technical narrative.                         |
| `severity`              | String  | Yes      | `INFORMATION`, `LOW`, `MEDIUM`, `HIGH`.                        |
| `confidence`            | String  | Yes      | `CERTAIN`, `FIRM`, `TENTATIVE`.                                |
| `baseUrl`               | String  | Yes      | URL where issue was found.                                     |
| `remediation`           | String  | No       | Recommended remediation.                                       |
| `background`            | String  | No       | Optional issue background.                                     |
| `remediationBackground` | String  | No       | Optional remediation background.                               |
| `typicalSeverity`       | String  | No       | Typical severity override (defaults to `severity`).            |
| `httpRequest`           | String  | No       | Raw HTTP request attachment.                                   |
| `httpResponseContent`   | String  | No       | Raw HTTP response attachment.                                  |
| `targetHostname`        | String  | No       | Host for attachment context.                                   |
| `targetPort`            | Int     | No       | Port for attachment context (default `443`).                   |
| `usesHttps`             | Boolean | No       | HTTPS flag for attachment context (default `true`).            |

If `httpRequest` is present, `targetHostname` must also be non-blank (with a valid positive `targetPort`); otherwise the handler returns an error instead of creating the issue. `httpResponseContent` is attached only together with `httpRequest`. Without an explicit request, the handler tries to find a matching Proxy history item by `baseUrl`.

## Recommended Practices

* Create issues after evidence is verified.
* Use `TENTATIVE` for suspected-only findings.
* Check duplicates before creating a new issue.
* Keep detail field evidence-based and reproducible.

## Example Usage

```json
{
  "name": "[AI] SQL Injection in user_id parameter",
  "detail": "The user_id parameter in GET /api/users is vulnerable to error-based SQL injection...",
  "severity": "HIGH",
  "confidence": "FIRM",
  "baseUrl": "https://example.com/api/users?user_id=1",
  "remediation": "Use parameterized queries and strict server-side validation."
}
```

## Integration Pattern

Typical chain:

1. Search/collect candidate requests (`proxy_http_history_regex`).
2. Validate behavior (`http1_request` / `http2_request`).
3. Summarize exploit evidence.
4. Create issue (`issue_create`).

The intermediate steps above use generic Montoya tools (`proxy_http_history_regex`, `http1_request`, `http2_request`), which are only present in the full build. In the BApp Store build, `issue_create` is still available, but pair it with PortSwigger's official Burp MCP Server (or `ai_findings_recent`) to gather and validate evidence. `issue_create` itself sends no AI request and does not depend on Burp's "Use AI" setting. `ai_passive_scan` does: in both builds it returns a tool error while "Use AI" is off for the extension, whatever backend is selected. PortSwigger documents "Use AI" as a per-extension checkbox, off by default: **Extensions > Installed > Custom AI Agent > Use AI**. See [Which Build?](https://burp-ai-agent.six2dez.com/getting-started/which-build.md).

See [Typical Workflows](https://burp-ai-agent.six2dez.com/examples/typical-workflows.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://burp-ai-agent.six2dez.com/mcp-server/issue-create.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
