> 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-project-test-case-note.md).

# Create Project Test Case Note

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

Adds a note to a test case in an AttackForge project. A note records **progress** working the test case - the running log of what the tester did and found. For reference material useful in performing the test case (background, tips, payloads) use `create_project_testcase_workspace_note` instead.

This is a **write** operation: it persists a new note against the project test case. The shape of `args` is declared inline (see Building args for Write Tools), so no preparatory call is needed. `note` is a rich-text field and must use the AttackForge richtext format described in the `richtext_format` block returned by `get_args_schema_for_tool`.

Files cannot be attached through this tool. Preconditions: the caller must have Edit access to the project and access to its test cases, and the test case must belong to the project. On success the new note 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_project_testcase_note` and click `Add`

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

* *Add a note to this test case saying no injection was found.*
* *Record on the TLS test case that the server still supports TLS 1.0.*
* *Log my testing progress on this test case.*

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

| Parameter | Type   | Required | Description                                     |
| --------- | ------ | -------- | ----------------------------------------------- |
| `args`    | object | Yes      | The note-creation payload - see the keys below. |

**`args` keys:**

| Key                   | Type   | Required | Description                                                                                                                                                                      |
| --------------------- | ------ | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `project_id`          | string | Yes      | Id (24-hex) of the project the test case is allocated to. Source: `find_projects`.                                                                                               |
| `project_testcase_id` | string | Yes      | Id (24-hex) of the project test case the note is being added to - the per-project instance, NOT the parent library test case. Source: `find_project_testcases` (its `id` field). |
| `note`                | string | Yes      | The note content - a record of progress working the test case. Rich-text - use the AttackForge richtext format.                                                                  |

#### Example Response

```json
{
  "id": "6650a4c08cade68ca7bc7192"
}
```


---

# 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-project-test-case-note.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.