> ## Documentation Index > Fetch the complete documentation index at: https://www.docusnap.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # MCP—Tools > Which tools Docusnap365 provides to your AI tool through MCP, which ones only read, and what to know before an AI tool changes data. Docusnap365 provides 27 tools to your AI tool. Each has exactly one job, such as searching risks or changing the processing state of a CVE finding. 19 tools read, eight change data. How to connect the AI tool is described under [MCP—Basics](https://www.docusnap.com/docs/en/api/mcp.md). ## Reading and changing Docusnap365 tells your AI tool for every tool whether it changes data. The reading tools are marked read-only. `create_comment` and `create_inventory_object` only add new data. `update_comment`, `delete_comment`, `update_risk`, `update_cve_status`, `update_inventory_object` and `delete_inventory_object` overwrite or remove existing data. The tools that change data require the matching access level. With the level *Viewer*, only the reading tools are available (see [Users › Module Access](https://www.docusnap.com/docs/en/settings/users.md#module-access)). Docusnap365 rejects a tool you are not allowed to use. ## ISMS | Tool | Does | | - | - | | `search_risks` | search risks, highest-rated first when no filter is set | | `get_risk` | read one risk in full | | `update_risk` | change the likelihood, impact, treatment, owner, review date, or name of a risk | | `search_controls` | search controls, including overdue ones | | `get_control` | read one control in full | | `search_assessments` | search the assessments of the activated regulations, one result per assessable objective | `update_risk` changes only the fields the AI tool specifies, and at least one. Likelihood and impact take values from 1 to 10 and can only be changed while the risk is in the lifecycle phase *Identified* or *Assessed*. ## CVE | Tool | Does | | - | - | | `search_cves` | search CVE findings, for example by CVE number, CVSS score, severity, or status | | `get_cve` | read one CVE finding by its id or its CVE number | | `list_affected_assets` | list the devices affected by a CVE finding | | `update_cve_status` | change the processing state, reason, owner, and due date of a CVE finding | The statuses *Accepted* and *False Positive* require a reason. A reason or due date can be removed by having the AI tool set it to empty. > [!NOTE] > > The CVE tools work with CVE findings from scans. The ISMS vulnerabilities are a different thing and are not part of them. ## ITAM | Tool | Does | | - | - | | `search_warranties` | search warranties, sorted by the end of coverage | | `search_itam_assets` | search the ITAM view of the inventory: lifecycle, criticality, end of life, validation, and completeness | | `search_cost_sources` | search the contracts and license agreements under ITAM › *Manage Costs* | The amounts and quantities from `search_cost_sources` refer to the current month. The response names it. ## Documents | Tool | Does | | - | - | | `search_documents` | search documents, most recently changed first | | `get_document` | read the properties of a document, without the content of its chapters | ## Inventory | Tool | Does | | - | - | | `list_object_types` | list the types, standard and self-defined | | `describe_object_type` | describe the fields of a type with data type and selectable values | | `search_inventory` | search assets, optionally with a device summary and fields of the type | | `get_inventory_object` | read an asset with all individual values of its type | | `create_inventory_object` | create an asset | | `update_inventory_object` | change the name, organization, location, and fields of an asset | | `delete_inventory_object` | delete an asset | The fields of a type differ from type to type. A search for field values in `search_inventory` therefore requires a type. Which fields a type carries is in the [data model](https://www.docusnap.com/docs/en/api/data-model.md). `search_inventory` can return CPU, RAM, model, manufacturer, and the number of installed software packages; you cannot filter by them. > [!NOTE] > > A deleted asset lands in the [Trash](https://www.docusnap.com/docs/en/getting-started/trash.md) and can be restored there. `delete_inventory_object` deletes assets only. The tool rejects an id that belongs to anything else. > [!NOTE] > > `create_inventory_object` rejects a name that an asset of the same type already carries, and names the existing asset. `update_inventory_object` rejects a rename for the same reason. An asset found by a scan cannot be renamed. ## Comments and relations | Tool | Does | | - | - | | `list_comments` | read the comments of a record in the order they were written | | `create_comment` | create a comment or a reply | | `update_comment` | replace the text of a comment | | `delete_comment` | delete a comment | | `list_relations` | read the relations of a record, grouped by the kind of the counterpart | Only your own comments can be changed or deleted. A record without comments and an id that belongs to no record return the same result. ## Shared rules of the search tools All tools whose names begin with `search_`, plus `list_comments` and `list_object_types`, behave the same way: | Parameter | Effect | | - | - | | `limit` | Number of results, default 25, at most 100. A value outside that range is rejected, not clamped. | | `sort_by` | Sorting by one of the offered options. For `cvss`, `score`, `affected_assets`, `modified`, `monthly_costs`, and `completeness`, an explicit choice sorts descending, for the others ascending, unless `sort_descending` says otherwise. | | `cursor` | Continues a search on the next page. It is valid only together with the parameters of the search it came from; otherwise the tool rejects it. | | `count_only` | Returns only the number of results. Up to 2000 results are counted; with more, the number is incomplete and the response advises narrowing the search. `count_only` cannot be combined with `cursor`. | A parameter the tool does not know is rejected. ## Related How to connect the AI tool, which permissions it has, and how the quota counts is described under [MCP—Basics](https://www.docusnap.com/docs/en/api/mcp.md). This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.