Update Project Test Case Lock

Description

Locks or unlocks an AttackForge project test case. Locking freezes the test case against further editing in the project. This is a write operation.

Use this tool - not patch_project_testcase - whenever you want to lock or unlock a project test case: patch_project_testcase cannot change the lock, and refuses to touch a test case while it is locked.

The shape of args is declared inline (see Building args for Write Tools), so no preparatory call is needed.

Preconditions: the caller must have at least View access to the project and be an Admin or Project Coordinator. On success the project 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 update_project_testcase_lock and click Add

Example Prompts

• Lock this test case in project X.

• Unlock the SQL injection test case so I can update it.

• Lock all the completed test cases on this project.

• Which test cases are locked, and can you unlock them?

Parameters

Parameter	Type	Required	Description
args	object	Yes	The lock-update 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 to lock or unlock - the per-project instance, NOT the parent library test case. Source: find_project_testcases (its id field).
locked	boolean	Yes	true to lock the test case, false to unlock it.

A locked test case is excluded from the project's test case counters, so locking or unlocking shifts the project's tested / not tested / total figures.

Example Response

{
  "id": "656168055d7035a12ade4cb3"
}