Patch Test Case

Description

Patches an existing AttackForge test case - the record carrying the descriptive fields (title, details, code, tags, sort_order, execution_flow). This is NOT the per-project test case that carries testing state; patch that with patch_project_testcase.

Two kinds of test case are patchable here, and which one it is determines what the caller needs:

• A library test case (source: find_testcases) - requires permission to patch library test cases (Admin or Project Operator).

• A project abuse case (source: the testcase_id on a project test case from find_project_testcases, resolvable via find_testcases testcase_ids) - requires Edit access to the owning project plus access to its test cases, and is refused while the project test case is locked.

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. On success the patched test case id 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 patch_testcase and click Add

Example Prompts

• Update the details on the SQL injection test case.

• Rename test case X.

• Add an execution flow step to this test case.

• Tag this test case as PCI relevant.

• Set the CWE custom field on test case X to CWE-89.

Parameters

Parameter	Type	Required	Description
args	object	Yes	The test-case-patch payload - see the keys below.

args keys:

Key	Type	Required	Description
testcase_id	string	Yes	Id (24-hex) of the test case to patch - either a library test case (source: find_testcases) or a project abuse case (source: the testcase_id on a project test case).
title	string	No	New title of the test case.
details	string	No	Details / description. Rich-text - use the AttackForge richtext format.
code	string	No	Arbitrary code associated with this test case.
tags	array	No	String tags. Replaces the existing tags when supplied.
sort_order	integer	No	Default sort order within the AttackForge UI.
execution_flow	array	No	Ordered execution-flow steps, each { title, details }. Replaces the existing execution flow when supplied.
custom_fields	array	No	Custom field values, each { key, value }. Supplying a custom field replaces its current value; supplying an empty value clears it. Discover keys via get_field_structure(model="testcase").

Example Response

{
  "id": "656168055d7035a12ade4cb3"
}