> 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/risk-commands.md).

# Risk Commands

* [getRiskyHosts](#getriskyhosts)
* [getRiskyUsers](#getriskyusers)

#### getRiskyHosts

***

Retrieves the risk score of a specific host, or the hosts with the highest risk scores in the environment.

<details>

<summary>Arguments</summary>

| Argument Name | Description                                                                                                            | Required |
| ------------- | ---------------------------------------------------------------------------------------------------------------------- | -------- |
| host\_id      | The host name of a specific host.                                                                                      | Optional |
| limit         | Limit the number of hosts that will appear in the list. (Use limit when no specific host is requested). Default is 10. | Optional |

</details>

<details>

<summary>Outputs</summary>

**Core.RiskyHost.type** *string*

Form of identification element.

**Core.RiskyHost.id** *string*

Identification value of the type field.

**Core.RiskyHost.score** *number*

The score assigned to the host.

**Core.RiskyHost.risk\_level** *string*

The risk level of the host.

**Core.RiskyHost.norm\_risk\_score** *number*

The normalized risk score of the host.

**Core.RiskyHost.reasons.date created** *string*

Date when the incident was created.

**Core.RiskyHost.reasons.description** *string*

Description of the incident.

**Core.RiskyHost.reasons.severity** *string*

The severity of the incident.

**Core.RiskyHost.reasons.status** *string*

The incident status.

**Core.RiskyHost.reasons.points** *number*

The score.

</details>

#### getRiskyUsers

***

Retrieves the risk score of a specific user, or the users with the highest risk scores in the environment.

<details>

<summary>Arguments</summary>

| Argument Name | Description                                                                                                                       | Required |
| ------------- | --------------------------------------------------------------------------------------------------------------------------------- | -------- |
| user\_id      | Unique ID of a specific user. User ID could be either of the `foo/dummy` format, or just `dummy`.                                 | Optional |
| limit         | Limit the number of users that will appear in the list. (limit should be used when no specific host is requested). Default is 10. | Optional |

</details>

<details>

<summary>Outputs</summary>

**Core.RiskyUser.type** *string*

Form of identification element.

**Core.RiskyUser.id** *string*

Identification value of the type field.

**Core.RiskyUser.score** *number*

The score assigned to the user.

**Core.RiskyUser.norm\_risk\_score** *number*

The normalized risk score of the user.

**Core.RiskyUser.reasons.date created** *string*

Date when the incident was created.

**Core.RiskyUser.reasons.description** *string*

Description of the incident.

**Core.RiskyUser.reasons.severity** *string*

The severity of the incident.

**Core.RiskyUser.reasons.status** *string*

The incident status.

**Core.RiskyUser.reasons.points** *number*

The score.

**Core.RiskyUser.risk\_level** *string*

The risk level of the user.

**Core.RiskyUser.email** *string*

The email address of the user.

</details>


---

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