Count Project Test Case Workspace Notes

Description

Returns the number of workspace notes recorded against the test cases of one AttackForge project. A workspace note is reference material useful for performing the test case - background, tips, payloads, or anything else worth having to hand while testing it. It is not a record of testing progress: for that, use count_project_testcase_notes instead.

Use this when you only need a total - call find_project_testcase_workspace_notes to retrieve the workspace notes themselves. The caller must have access to the project's test cases; if not, an access-denied error is returned.

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

Example Prompts

• How many workspace notes are on project X?

• How many reference notes does this test case have?

• How many workspace notes mention payloads?

• How many workspace notes were added to this project this month?

Parameters

Parameter	Type	Required	Description
project_id	string	Yes	Id (24-hex) of the project whose test case workspace notes you want to count. Source: find_projects. The caller must have access to this project's test cases.
project_testcase_ids	array	No	Restrict the count to these project test cases (array of 24-hex ids). Source: find_project_testcases (its id field). Omit to count 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 - a workspace note must satisfy all of them to be counted. Supported fields are listed below.

Supported filter fields:

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

Workspace 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. title is plain text and has no such caveat.

Example Response

{
  "count": 9
}