> 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-commands-guide/cortex-commands-overview.md).

# Cortex Commands Overview

Use Cortex commands to investigate, respond, and manage Cortex platform data.

You can use commands in playbooks and in the War Room to retrieve data, automate decisions, and take response actions.

This guide covers commands for **Cortex XSIAM**, **Cortex XDR 5.x**, **Cortex Cloud Runtime**, **Cortex Cloud Posture**, and **Cortex AgentiX**.

Each command reference describes its arguments and outputs.

{% hint style="info" %}
**NOTE**

Not all commands are available in every Cortex product. Command availability depends on your product license. 
{% endhint %}

## What you can do with commands

Cortex commands help you investigate, respond, and manage workflows.

For example, you can:

* Retrieve and update cases.
* Create, review, and organize timeline records and evidence.
* Retrieve files from endpoints and check action status.
* Manage file allowlist and blocklist entries by hash.
* Query assets and trigger vulnerability scans.
* Create AppSec policies for repositories and deployed assets.
* Search, create, and update indicators.
* Manage users, groups, and API keys.


---

# 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-commands-guide/cortex-commands-overview.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.