# Anti-Nuke Overview

> Anti-Nuke protects your server by limiting dangerous actions. When a user exceeds the allowed limit, they receive an automatic punishment.

## How It Works

Anti-Nuke monitors specific dangerous actions performed by moderators and admins. Each action type has a configurable limit. When someone exceeds their limit within the 10-minute window, Security automatically punishes them.

## Monitored Actions

| Action                       | Description                      |
| ---------------------------- | -------------------------------- |
| Banning members              | Mass ban protection              |
| Kicking members              | Mass kick protection             |
| Deleting channels            | Channel deletion protection      |
| Creating channels            | Channel creation spam protection |
| Deleting roles               | Role deletion protection         |
| Creating roles               | Role creation spam protection    |
| Adding bots                  | Unauthorized bot protection      |
| Giving dangerous permissions | Permission escalation protection |
| Adding dangerous roles       | Role assignment protection       |
| Pruning members              | Mass prune protection            |

## Reset Duration

Action counters reset every **10 minutes**. This duration is fixed and cannot be changed. Set your limits accordingly.

**Example:** If the ban limit is 3, a user can ban up to 3 members within any 10-minute window. After 10 minutes, their counter resets.

## Who Is Exempt from Punishment?

Users are **not punished** if any of these conditions apply:

| Condition                                              | Description                   |
| ------------------------------------------------------ | ----------------------------- |
| User is whitelisted for the action                     | Specific action bypass        |
| User is globally whitelisted                           | All actions bypass            |
| User has a whitelisted role for the action             | Role-based action bypass      |
| User has a globally whitelisted role                   | Role-based all actions bypass |
| User is the server owner                               | Owners are always exempt      |
| User's role is equal to or higher than Security's role | Role hierarchy protection     |
| The action trigger is disabled                         | Action not being monitored    |

## Configuration

* [Check Settings](https://docs.securitybot.gg/anti-nuke/anti-nuke/check-settings) - View current Anti-Nuke configuration
* [Changing Limits](https://docs.securitybot.gg/anti-nuke/anti-nuke/changing-limits) - Modify action limits
* [Changing Punishments](https://docs.securitybot.gg/anti-nuke/anti-nuke/changing-punishments) - Set punishment types
* [Enable/Disable Triggers](https://docs.securitybot.gg/anti-nuke/anti-nuke/enable-disable-action-triggers) - Toggle action monitoring
* [Dangerous Permissions](https://docs.securitybot.gg/anti-nuke/anti-nuke/dangerous-permissions) - Permission reference list

## Related

* [Whitelist](https://docs.securitybot.gg/whitelist/whitelist) - Exempt trusted users and roles
* [Beast Mode](https://docs.securitybot.gg/other-modules/beast-mode) - Global score-based protection


---

# Agent Instructions: 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:

```
GET https://docs.securitybot.gg/anti-nuke/anti-nuke.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.