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

# Exclusions Commands

* [getExclusions](#getexclusions)
* [addExclusion](#addexclusion)
* [deleteExclusion](#deleteexclusion)

#### getExclusions

***

Retrieves a list of issue exclusions. If no arguments are provided, all exclusions will be returned.

<details>

<summary>Arguments</summary>

| Argument Name  | Description                                                                                                                                          | Required |
| -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- | -------- |
| filter\_object | Filter object for the exclusion. Example: {"filter":{"AND":\[{"SEARCH\_FIELD":"alert\_category","SEARCH\_TYPE":"NEQ","SEARCH\_VALUE":"Phishing"}]}}. | Optional |
| limit          | Maximum number of exclusions to return. Default is 20.                                                                                               | Optional |

</details>

<details>

<summary>Outputs</summary>

**Core.Exclusion.ALERT\_WHITELIST\_ID** *number*

Exclusion ID.

**Core.Exclusion.ALERT\_WHITELIST\_MODIFY\_TIME** *number*

Exclusion modification time.

**Core.Exclusion.ALERT\_WHITELIST\_NAME** *string*

Exclusion name.

**Core.Exclusion.ALERT\_WHITELIST\_HITS** *number*

Exclusion hits count.

**Core.Exclusion.ALERT\_WHITELIST\_COMMENT** *string*

Exclusion comment.

**Core.Exclusion.ALERT\_WHITELIST\_USER** *string*

Exclusion user.

**Core.Exclusion.ALERT\_WHITELIST\_PRETTY\_USER** *string*

Exclusion pretty user name.

**Core.Exclusion.ALERT\_WHITELIST\_STATUS** *string*

Exclusion status.

**Core.Exclusion.ALERT\_WHITELIST\_BACKWARDS\_SCAN\_STATUS** *string*

Exclusion backwards scan status.

**Core.Exclusion.ALERT\_WHITELIST\_MIGRATED\_FROM\_ANALYTICS** *number*

Whether the exclusion was migrated from analytics.

</details>

#### addExclusion

***

Adds an alert exclusion rule. Alerts matching the filter criteria will be suppressed moving forward.

<details>

<summary>Arguments</summary>

| Argument Name  | Description                                                                                   | Required |
| -------------- | --------------------------------------------------------------------------------------------- | -------- |
| name           | Name of the exclusion rule.                                                                   | Required |
| filter\_object | A JSON object defining the filter for the exclusion.                                          | Required |
| status         | The status of the exclusion rule. Possible values are: ENABLED, DISABLED. Default is ENABLED. | Optional |

</details>

<details>

<summary>Outputs</summary>

**Core.Exclusion.rule\_id** *number*

The ID of the created exclusion rule.

</details>

#### deleteExclusion

***

Deletes an alert exclusion rule. Alerts matching the filter criteria will be raised moving forward.

<details>

<summary>Arguments</summary>

| Argument Name        | Description                             | Required |
| -------------------- | --------------------------------------- | -------- |
| alert\_exclusion\_id | The ID of the exclusion rule to delete. | Required |

</details>

<details>

<summary>Outputs</summary>

**Core.DeletedExclusion.rule\_id** *number*

The IDs of the deleted exclusion rules.

</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/exclusions-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.