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

# Patch Project Test Case Workspace Note

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

Updates an existing workspace note on a test case in an AttackForge project. A workspace note is **reference material** useful for performing the test case. To update the record of testing progress instead, use `patch_project_testcase_note`.

This is a **write** operation. The shape of `args` is declared inline (see Building args for Write Tools), so no preparatory call is needed. Only the fields supplied in `args` are changed; omitted fields are left untouched, and **at least one** of `title` or `note` must be supplied. `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`.

The workspace note keeps its original author; patching does not reassign it to the caller. Preconditions: the workspace note must exist, and the caller must have Edit access to the project the workspace note's test case belongs to, plus access to that project's test cases. On success the patched workspace 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 `patch_project_testcase_workspace_note` and click `Add`

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

* *Rename this workspace note to "SQLi payloads".*
* *Add another payload to the workspace note on this test case.*
* *Update the reference material on this test case with the new endpoint.*

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

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

**`args` keys:**

| Key                                  | Type   | Required | Description                                                                                                                                 |
| ------------------------------------ | ------ | -------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
| `project_testcase_workspace_note_id` | string | Yes      | Id (24-hex) of the project test case workspace note to update. Source: `find_project_testcase_workspace_notes` (its `id` field).            |
| `title`                              | string | No       | The new title, which replaces the existing title. Plain text. Omit to leave the title unchanged.                                            |
| `note`                               | string | No       | The new content, which replaces the existing content. Rich-text - use the AttackForge richtext format. Omit to leave the content unchanged. |

> At least one of `title` or `note` must be supplied.

#### 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/patch-project-test-case-workspace-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.