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

# Patch Project Scope

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

Bulk adds, updates, or removes Project Scope items on a single AttackForge project. A Project Scope item represents one thing within the testing scope of a project (URL, host, application, etc.). One call can mix create/patch/delete operations across multiple scope items - the exact shape of those operations is defined in the args schema.

A two-step workflow is **required** because the input shape is tenant-specific - see Two-Step Workflow for Write Tools:

1. Call `get_args_schema_for_tool(tool="patch_project_scope")` to retrieve the current JSON Schema for `args`.
2. Build `args` to match that schema and call this tool.

The schema always requires `project_id` (source: `find_projects`); it also describes how to target existing scope items (source: `find_project_scope`) for update/delete and how to declare new items for creation. Preconditions: the caller must have Edit access to the target project. On success the project id 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 `patch_project_scope` and click `Add`

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

* *Add these three URLs to the scope of project X.*
* *Remove the out-of-scope host from project X.*
* *Update the details on a scope item in project X.*
* *Replace the scope of the ACME project with this list of assets.*

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

| Parameter | Type   | Required | Description                                                                                                                                                                                         |
| --------- | ------ | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `args`    | object | Yes      | The project-scope patch payload. Build it to satisfy `get_args_schema_for_tool(tool="patch_project_scope")`. Always requires `project_id`; describes create/patch/delete operations on scope items. |

#### Example Response

```json
{
  "id": "656168055d7035a12ade4cb3"
}
```


---

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