> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xdr-5.x/configure-cortex-xdr/configure-and-deploy-cortex-xdr/cortex-mcp-server/use-the-cortex-mcp-server.md).

# Use the Cortex MCP server

Investigate Cortex data with built-in MCP tools.

The Cortex MCP server provides built-in tools to manage cases and issues and conduct investigations.

### Built-in tools

Built-in tools include, but are not limited to:

* `get_assets` retrieves all assets or a filtered subset.
* `get_assets_by_id` retrieves details for one asset.
* `get_cases` retrieves cases by criteria such as domain, status, or severity.
* `get_issues` retrieves issues by criteria such as domain, severity, or detection method.
* `get_assessment_profile_results` retrieves compliance-assessment results.
* `get_filtered_endpoints` retrieves endpoints using agent status and other filters.

When you run the `update` command in the Cortex MCP server, new or updated tools provided by Cortex are automatically downloaded.

You also have the flexibility to create and customize your own tools to fit specific use cases and workflows. For more information, see [Create custom Cortex MCP server tools](/cortex-xdr-5.x/configure-cortex-xdr/configure-and-deploy-cortex-xdr/cortex-mcp-server/create-custom-cortex-mcp-server-tools.md).

{% hint style="info" %}

### Note

The built-in tools retrieve information, but do not write to the tenant. You can create your own tools that include write actions. The examples below include both.
{% endhint %}

### Use case examples

* Show the ten most critical cases. Create a graph for management.
* Give details for case ID `12345`. Create a visual timeline.
* Isolate endpoint `WIN-123` because it may be compromised.
* Retrieve full details for endpoint `XXXX`.
* Add a note to case `12345`: “Escalated to Tier 2 for further investigation.”


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-xdr-5.x/configure-cortex-xdr/configure-and-deploy-cortex-xdr/cortex-mcp-server/use-the-cortex-mcp-server.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.