> 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-cloud-posture-management/onboard-and-configure/post-deployment-steps/cortex-mcp-server/use-the-cortex-mcp-server.md).

# Use the Cortex MCP server

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

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

* **get\_assets**: Fetch all assets, or a filtered subset of assets, based on criteria such as category, region or provider.
* **get\_assets\_by\_id**: Fetch detailed information about the asset specified by the asset ID.
* **get\_cases**: Fetch all cases, or a filtered subset of cases matching specific criteria such as domain, status, severity or specific case Id.
* **get\_issues**: Fetch all issues, or a filtered subset of issues matching specific criteria such as domain, severity, detection method or specific issue ID.
* **get\_assessment\_profile\_results**: Fetch the results of all or filtered compliance assessments from the Cortex platform.
* **get\_filtered\_endpoints**: Fetch a filtered list of endpoints managed by the XDR agents based on their status, XDR 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-cloud-posture-management/onboard-and-configure/post-deployment-steps/cortex-mcp-server/create-custom-cortex-mcp-server-tools.md).

### **Use case examples**

{% hint style="info" %}
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 %}

* Show me the top ten most critical cases and create a graphical representation for my manager to review.
* Give me the details for case ID 12345 and 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 saying ‘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 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://cortex-docs.paloaltonetworks.com/cortex-cloud-posture-management/onboard-and-configure/post-deployment-steps/cortex-mcp-server/use-the-cortex-mcp-server.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.