> 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-scope.md).

# Count Project Scope

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

Returns the number of Project Scope items belonging to one AttackForge project. A Project Scope item represents one thing that is within the testing scope of that project (a URL, host, application, etc.). Use this when you only need a total - call `find_project_scope` to retrieve the items themselves. The caller must have at least View access to the project; if not, an access-denied error is returned.

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

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

* *How many scope items are in project X?*
* *How many scope items in project X are linked to an asset?*
* *How many in-scope URLs does the ACME project have?*

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

| Parameter    | Type   | Required | Description                                                                                                                               |
| ------------ | ------ | -------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
| `project_id` | string | Yes      | The id (24-hex) of the project whose scope you want to count. Obtain it from `find_projects`. The caller must have View access or higher. |
| `filter`     | object | No       | A MongoDB-style filter. Supported fields are listed below.                                                                                |

**Supported `filter` fields:**

| Field      | Type                   | Description                                                                                                  |
| ---------- | ---------------------- | ------------------------------------------------------------------------------------------------------------ |
| `id`       | `ObjectId('<24 hex>')` | the Project Scope item id                                                                                    |
| `name`     | string                 | the scope item name (URL, host, application, etc.)                                                           |
| `asset_id` | `ObjectId('<24 hex>')` | id of the linked Asset (only set when the Assets module is enabled and the scope item is linked to an Asset) |

#### Example Response

```json
{
  "count": 12
}
```


---

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