> For the complete documentation index, see [llms.txt](https://support.attackforge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.attackforge.com/app/modules/ai-mcp-and-skills/create-vulnerability.md).

# Create Vulnerability

#### Description <a href="#description" id="description"></a>

Creates a new AttackForge vulnerability (also called a finding or issue) inside an existing project. Every vulnerability is linked to a project (`project_id`) and to a writeup template (`writeup_id`), which seeds its title/description/remediation.

A two-step workflow is **required** because the input shape is tenant-specific - see Two-Step Workflow for Write Tools:

1. Call `get_args_schema_for_tool(tool="create_vulnerability")` to retrieve the current JSON Schema for `args`.
2. Build `args` to match that schema and call this tool.

Preconditions: the caller needs Edit access to the target project, View access to the chosen writeup, the project must be under its per-project vulnerability-creation limit, and (for non-Cloud/Server licences) Client-role users cannot create vulnerabilities. Any rich-text field must use the AttackForge richtext format from the `richtext_format` block. On success the new vulnerability id is returned.

#### How To Enable <a href="#how-to-enable" id="how-to-enable"></a>

1. Go to `Users`
2. Select the user you would like to provide access to this tool
3. Click on `Access > MCP`
4. Click on `Add Tools`
5. Select the tool `create_vulnerability` and click `Add`

#### Example Prompts <a href="#example-prompts" id="example-prompts"></a>

* *Create a High SQL Injection finding in project X using the "SQL Injection" writeup.*
* *Add a new vulnerability to project X based on writeup Y with these steps to reproduce.*
* *Log a critical finding against the login asset in the ACME project.*

#### Parameters <a href="#parameters" id="parameters"></a>

| Parameter | Type   | Required | Description                                                                                                                                                                                                                 |
| --------- | ------ | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `args`    | object | Yes      | The vulnerability-creation payload. Build it to satisfy `get_args_schema_for_tool(tool="create_vulnerability")`. At minimum requires a `project_id` (source: `find_projects`) and a `writeup_id` (source: `find_writeups`). |

#### Example Response

```json
{
  "id": "656168055d7035a12ade4cb3"
}
```


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://support.attackforge.com/app/modules/ai-mcp-and-skills/create-vulnerability.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.