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

# Find Project Requests

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

Lists AttackForge project requests matching the optional `filter`. Use this when you need the actual records - call `count_project_requests` when only a total is needed. Results are automatically scoped to project requests the calling user can access (non-admin users only see project requests they have View access to). Returns an empty result set when project requests are disabled for the tenant (`frontend.enable_project_requests`). Results are paginated (default 10 per page, max 50).

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

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

* *Show me all project requests pending approval.*
* *List project requests that require onsite testing, including the reason testing is required.*
* *Find project requests with a desired start date after January 2026.*
* *Show me the scope and desired testing window for project request X.*

#### 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 (`id` is always returned). Supported values are listed below.      |
| `custom_field_keys` | array   | No       | Custom field keys to include (discover via `get_field_structure(model="project-request")`). |
| `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`, `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 }`                                 |

**Supported `fields` values:**

| Field                        | Type                                                                               |
| ---------------------------- | ---------------------------------------------------------------------------------- |
| `id`                         | string                                                                             |
| `created`, `modified`        | ISO-8601 datetime                                                                  |
| `status`                     | one of `'Pending Approval'`, `'Approved'`, `'Rejected'`, `'Requested Information'` |
| `name`, `code`               | string                                                                             |
| `organization_code`          | string                                                                             |
| `testsuite_ids`              | array of string                                                                    |
| `scope`                      | string                                                                             |
| `reason_testing_is_required` | string                                                                             |
| `desired_start_date`         | ISO-8601 datetime                                                                  |
| `desired_end_date`           | ISO-8601 datetime                                                                  |
| `desired_testing_window`     | string                                                                             |
| `onsite_testing_required`    | one of `'Yes'`, `'No'`                                                             |
| `linked_group_ids`           | array of string                                                                    |

#### Example Response

```json
{
  "data": [
    {
      "id": "6650a4c08cade68ca7bc7192",
      "created": "2026-01-12T09:14:00.000Z",
      "modified": "2026-01-13T10:02:00.000Z",
      "status": "Pending Approval",
      "name": "ACME Web App Pentest",
      "code": "ACME-WEB",
      "organization_code": "ACME",
      "scope": "https://app.acme.example and supporting APIs",
      "reason_testing_is_required": "Annual compliance requirement",
      "desired_start_date": "2026-02-01T00:00:00.000Z",
      "desired_end_date": "2026-02-14T00:00:00.000Z",
      "desired_testing_window": "Business hours",
      "onsite_testing_required": "No",
      "linked_group_ids": [
        "65a440c08cade68ca7bc7000"
      ],
      "custom_fields": [
        {
          "key": "engagement_type",
          "value": "pentest",
          "label": "Engagement Type"
        }
      ]
    }
  ],
  "count": 1,
  "total": 1
}
```


---

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