> 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/find-test-suites.md).

# Find Test Suites

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

Lists AttackForge testsuites matching the optional `filter`. A testsuite is a reusable methodology - a named, taggable collection of test cases that can be added to a project's testing plan or proposed on a project request. Use this when you need the actual records - call `count_testsuites` when only a total is needed. Results are paginated (default 10 per page, max 50).

Use the ids returned here to scope `find_testcases` / `count_testcases` via their `testsuite_ids` parameter. See Test Cases and Methodology.

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

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

* *Show me all my testsuites.*
* *Find the testsuite for web application testing.*
* *Which testsuites can be selected on a project request?*
* *List testsuites tagged OWASP Top 10 with their descriptions.*
* *Show me the testsuites in the order they appear in the UI.*
* *What is the code for the mobile testing methodology?*

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

| Parameter | Type    | Required | Description                                                                                              |
| --------- | ------- | -------- | -------------------------------------------------------------------------------------------------------- |
| `filter`  | object  | No       | A MongoDB-style filter. Supported fields are listed below.                                               |
| `fields`  | array   | No       | System fields to include on each testsuite (`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>')`                             |
| `created`, `modified`            | ISO-8601 datetime                                  |
| `name`                           | string                                             |
| `code`                           | string                                             |
| `is_visible_on_project_requests` | boolean - supports `$eq`, `$ne` and `$exists` only |
| `tags`                           | array of string                                    |
| `user_id`                        | `ObjectId('<24 hex>')`                             |

**Supported `fields` values:**

| Field                            | Type              |
| -------------------------------- | ----------------- |
| `id`                             | string            |
| `created`, `modified`            | ISO-8601 datetime |
| `name`                           | string            |
| `code`                           | string            |
| `description`                    | string            |
| `is_visible_on_project_requests` | boolean           |
| `sort_order`                     | integer           |
| `tags`                           | array of string   |
| `user_id`                        | string            |

#### Example Response

```json
{
  "data": [
    {
      "id": "65a440c08cade68ca7bc7192",
      "created": "2024-01-14T22:41:04.118Z",
      "modified": "2026-02-02T11:07:35.902Z",
      "name": "Web Application Testing",
      "code": "WEB",
      "description": "Methodology for testing web applications, aligned to the OWASP Testing Guide.",
      "is_visible_on_project_requests": true,
      "sort_order": 1,
      "tags": [
        "owasp-top-10",
        "web"
      ],
      "user_id": "5ad737d6e576e6290aff1808"
    }
  ],
  "count": 1,
  "total": 24
}
```


---

# 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/find-test-suites.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.