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

# Find Assets

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

Lists AttackForge Assets matching the optional `filter`, scoped to one or more asset libraries. Use this when you need the actual asset records - call `count_assets` when only a total is needed. Requires the Assets module to be enabled; otherwise returns an error. 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_assets` and click `Add`

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

* *Show me all my assets. Include custom fields in the response.*
* *Find assets with "router" in the name.*
* *List all Infrastructure assets with their external asset IDs.*
* *Show me the assets in a specific custom library.*
* *Which assets are tagged production?*

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

| Parameter           | Type    | Required | Description                                                                                                                                                                                |
| ------------------- | ------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `asset_library_key` | string  | No       | Scope of asset libraries to search (`"all"` default, `"my"`, `"uncatalogued"`, or a 24-char custom library id). **Do NOT** filter on library membership via `filter` - use this parameter. |
| `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="asset")`).                                                                                                          |
| `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`                | string                                             |
| `asset_type`          | string                                             |
| `external_asset_id`   | string                                             |
| `custom_fields`       | array of `{ key: string, value: string or array }` |

**Supported `fields` values:**

| Field                 | Type              |
| --------------------- | ----------------- |
| `id`                  | string            |
| `name`                | string            |
| `created`, `modified` | ISO-8601 datetime |
| `asset_type`          | string            |
| `external_asset_id`   | string            |
| `details`             | string            |

#### Example Response

```json
{
  "data": [
    {
      "id": "64e17a99009140000f4acf70",
      "name": "192.168.0.1",
      "created": "2023-08-19T10:01:29.000Z",
      "modified": "2025-05-21T08:54:09.000Z",
      "asset_type": "Infrastructure",
      "external_asset_id": "CMDB-123",
      "details": "This asset is the main router for the head office",
      "custom_fields": [
        {
          "key": "internet_facing",
          "value": "Yes",
          "label": "Internet Facing"
        },
        {
          "key": "subnets",
          "value": [
            "192.168.0.0/24"
          ],
          "label": "Subnets"
        }
      ]
    }
  ],
  "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-assets.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.