> 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/count-test-cases.md).

# Count Test Cases

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

Returns the number of AttackForge **library** test cases matching the optional `filter`. A library test case is a reusable, taggable unit of testing methodology that belongs to a testsuite - it is NOT a per-project test case (see `count_project_testcases` for those). Use this when you only need a total - call `find_testcases` to retrieve the records.

Scope the count to specific testsuites via `testsuite_ids`. 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 `count_testcases` and click `Add`

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

* *How many test cases are in my methodology library?*
* *How many test cases are in the web application testsuite?*
* *How many test cases are tagged OWASP Top 10?*
* *How many test cases mention injection?*

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

| Parameter       | Type   | Required | Description                                                                                                                                                                  |
| --------------- | ------ | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `testsuite_ids` | array  | No       | Restrict the count to test cases belonging to these testsuites (array of 24-hex ids). Source: `find_testsuites`. Omit to count across every testsuite the caller can access. |
| `filter`        | object | No       | A MongoDB-style filter. Supported fields are listed below.                                                                                                                   |

**Supported `filter` fields:**

| Field                  | Type / Values                                      |
| ---------------------- | -------------------------------------------------- |
| `id`                   | `ObjectId('<24 hex>')`                             |
| `created`, `modified`  | ISO-8601 datetime                                  |
| `title`                | string                                             |
| `code`                 | string                                             |
| `tags`                 | array of string                                    |
| `sort_order`           | integer                                            |
| `custom_fields`        | array of `{ key: string, value: string or array }` |
| `library_id`           | string                                             |
| `template_testcase_id` | `ObjectId('<24 hex>')`                             |
| `user_id`              | `ObjectId('<24 hex>')`                             |

> Do NOT filter on testsuite membership via `filter` - `testsuite_id` is disallowed there. Use the `testsuite_ids` parameter.

#### Example Response

```json
{
  "count": 412
}
```


---

# 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/count-test-cases.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.