> 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-project-requests.md).

# Count Project Requests

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

Returns the number of AttackForge project requests matching the optional `filter`. Use this when you only need a total - call `find_project_requests` for the records. Results are automatically scoped to project requests the calling user can access (non-admin users only count project requests they have View access to). Returns `0` when project requests are disabled for the tenant (`frontend.enable_project_requests`).

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

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

* *How many project requests are pending approval?*
* *How many project requests require onsite testing?*
* *How many project requests were submitted this quarter?*
* *How many project requests have been rejected?*

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

| Parameter | Type   | Required | Description                                                |
| --------- | ------ | -------- | ---------------------------------------------------------- |
| `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                                                                  |
| `name`, `code`            | string                                                                             |
| `organization_code`       | string                                                                             |
| `status`                  | one of `'Pending Approval'`, `'Approved'`, `'Rejected'`, `'Requested Information'` |
| `desired_start_date`      | ISO-8601 datetime                                                                  |
| `desired_end_date`        | ISO-8601 datetime                                                                  |
| `onsite_testing_required` | one of `'Yes'`, `'No'`                                                             |
| `custom_fields`           | array of `{ key: string, value: string or array }`                                 |

#### Example Response

```json
{
  "count": 7
}
```


---

# 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-project-requests.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.