Find Project Test Case Notes

Description

Lists the notes recorded against the test cases of one AttackForge project. A note records progress working the test case - the running log of what the tester did and found, and is what to read when you want to know how testing is going. For reference material useful in performing a test case (background, tips, payloads) use find_project_testcase_workspace_notes instead.

A note may carry attached files; each is listed in files and can be fetched with get_file. Notes live here rather than on find_project_testcases because one test case can carry many of them.

The caller must have access to the project's test cases. Results are paginated (default 10 per page, max 50).

How To Enable

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 find_project_testcase_notes and click Add

Example Prompts

• Show me the testing notes for project X.

• What progress has been recorded on this test case?

• Summarise the testing notes on the ACME project this week.

• Which notes on project X mention TLS?

• Who has been recording notes on this project?

• Show me the files attached to the notes on this test case.

Parameters

Parameter	Type	Required	Description
project_id	string	Yes	Id (24-hex) of the project whose test case notes you want to list. Source: find_projects. The caller must have access to this project's test cases.
project_testcase_ids	array	No	Restrict the results to these project test cases (array of 24-hex ids). Source: find_project_testcases (its id field). Omit to return notes across every test case in the project. Ids that do not belong to this project are ignored.
filter	object	No	A MongoDB-style filter, applied on top of project_id and project_testcase_ids. Supported fields are listed below.
fields	array	No	Fields to include on each note (id is always returned). Supported values are listed below.
limit	integer	No	Maximum records to return in this page. Default 10, max 50.
skip	integer	No	Number of records to skip (offset). Default 0.

Supported filter fields:

Field	Type / Values
id	ObjectId('<24 hex>')
project_testcase_id	ObjectId('<24 hex>')
created, modified	ISO-8601 datetime
note	string
user_id	ObjectId('<24 hex>')

Notes are stored as AttackForge richtext (HTML), so a $regex on note matches the markup as stored, not the rendered text. Keep patterns to plain words to avoid matching tags.

Supported fields values:

Field	Type
id	string
project_testcase_id	string
created, modified	ISO-8601 datetime
note	string (AttackForge richtext)
note_format	string
user_id	string
files	array of { id, created, modified, name, mimeType, hash, size, storage_name, storage_location }

Example Response

{
  "data": [
    {
      "id": "6990ae21c4b7f3d2e1904471",
      "project_testcase_id": "6987c31b8e7d46a8089d9b54",
      "created": "2026-03-11T15:22:47.118Z",
      "modified": "2026-03-11T15:22:47.118Z",
      "note": "<p>Tested all 14 parameters on the search endpoint with boolean and time-based payloads. No injection observed - responses are consistent and the backend uses prepared statements.</p>",
      "note_format": "richtext",
      "user_id": "5ad737d6e576e6290aff1808",
      "files": []
    }
  ],
  "count": 1,
  "total": 31
}