> 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/create-test-suite.md).

# Create Test Suite

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

Creates a new AttackForge testsuite - a reusable methodology that test cases belong to. This is a **write** operation: it persists a new testsuite record.

The shape of `args` is declared inline (see Building args for Write Tools), so no preparatory call is needed. Preconditions: the caller must have permission to create testsuites. On success the new testsuite id is returned.

Add test cases to the new testsuite with `create_testcase`.

#### 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 `create_testsuite` and click `Add`

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

* *Create a testsuite called "API Security Testing".*
* *Set up a new methodology for cloud configuration reviews and tag it "cloud".*
* *Create an internal-only testsuite that should not appear on project requests.*

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

| Parameter | Type   | Required | Description                                          |
| --------- | ------ | -------- | ---------------------------------------------------- |
| `args`    | object | Yes      | The testsuite-creation payload - see the keys below. |

**`args` keys:**

| Key                              | Type    | Required | Description                                                                             |
| -------------------------------- | ------- | -------- | --------------------------------------------------------------------------------------- |
| `name`                           | string  | Yes      | Name of the testsuite.                                                                  |
| `description`                    | string  | Yes      | Description of the testsuite.                                                           |
| `is_visible_on_project_requests` | boolean | Yes      | Whether the testsuite is offered in the AttackForge UI when creating a Project Request. |
| `code`                           | string  | No       | Arbitrary code associated with this testsuite.                                          |
| `sort_order`                     | integer | No       | Determines the default sort order within the AttackForge UI.                            |
| `tags`                           | array   | No       | String tags attached to this testsuite.                                                 |

#### Example Response

```json
{
  "id": "65a440c08cade68ca7bc7192"
}
```


---

# 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/create-test-suite.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.