> ## Documentation Index > Fetch the complete documentation index at: https://docs.vetox.io/llms.txt > Use this file to discover all available pages before exploring further. # Protection > Rate-limit destructive actions so a compromised moderator account or rogue bot cannot damage your server. Free on every tier. Auto-Moderation and Anti-Raid defend against outsiders. Protection defends against **trusted accounts** — a moderator whose account is stolen, or a bot that turns out to be malicious. Free on every tier. ## Master settings | Setting | Default | Effect | | ---------------------------------- | ------- | ----------------------------------------------------------------------------------- | | **Log Channel** | None | Where Protection reports what it did | | **DM on Punishment** | Off | Tell the punished member why | | **Strip only privileged roles** | Off | With Remove Roles, take only roles holding a dangerous permission and keep the rest | | **Let Manage Roles restore roles** | Off | Whether anyone with Manage Roles may restore a punished member's roles | ## Whitelist Whitelisted roles and users are exempt from every rule. Whitelisting is exactly the hole an attacker needs. Whitelist as few accounts as possible — ideally none. The **server owner is always exempt** and cannot be protected against. ## What it watches Twenty rules across five groups: **Member Actions** (banning, kicking) · **Role Management** (create, delete, rename, granting a dangerous role, adding dangerous permissions) · **Channel Management** (create, delete, rename) · **Server Settings** (rename, icon) · **Other Protections** (adding bots, emoji, invites, webhooks, stickers, scheduled events). All are disabled by default. Rules marked **Instant** act on the first occurrence and have no count or window. The rest let you set a limit. ## Configuring a rule | Setting | Default | Notes | | --------------- | ------- | -------------------------------------------------- | | **Limit Mode** | — | Count only, or count within a time window | | **Limit** | — | 1 to 100 | | **Duration** | — | 1 to 60 minutes, in duration mode | | **Punishment** | Ban | Ban, Kick or Remove Roles | | **Undo Action** | On | Reverses what they did, where reversal is possible | **Channel deletion and role deletion ignore your limit mode and duration entirely.** Both always use a fixed **10-second** window, whatever you configure. The settings save but have no effect on those two rules. In **Count only** mode the counter does not decay. It accumulates until the rule fires or the bot restarts, so an action taken today can combine with one from last week. Use **With Duration** if you want a rolling window. Not everything can be undone — deleted roles and channels cannot be restored, and kicks cannot be reversed. Each rule states its own undo behaviour. ## Dangerous permissions Protection treats some permissions as high-risk, defaulting to Administrator, Ban Members, Kick Members and Manage Roles. You can also include Manage Channels, Manage Server, Manage Webhooks and Mention Everyone. This is a **single shared list**, not per-rule. Changing it on one rule changes it for every rule that uses it. ## Command limits Separately, you can rate-limit Vetox's own moderation commands: Ban, Kick, Timeout, Mute, Voice Mute and Role. This catches a moderator mass-banning through the bot rather than through Discord directly. The Role command additionally supports allowed roles, restricted roles, and dangerous-permission detection — a role carrying a dangerous permission is both counted and automatically removed from the target. ## Role-based overrides Set different limits per role. A junior moderator role can be held to two bans an hour while your admin role gets twenty. A per-role entry that is **disabled** acts as an explicit opt-out — that role is exempted from the global rule entirely, rather than falling back to it. **Adding a role copies your current global configuration into it**, including changes you have not saved yet. It does not start from defaults. Review the new role's settings before saving. ## How a rule fires Only entries from the last few seconds are considered, so an old action is never attributed to the wrong person. Server owner, whitelisted users and roles, and any per-role opt-out. When it reaches your limit, the rule triggers. Optionally with a DM, and a report to your log channel. Vetox never punishes itself, and cannot act on the server owner. ## Two limitations worth knowing **The Anti-Vanity-Change protection is not shown on this page, and saving here erases it.** That protection exists and works, but has no card in the dashboard. Because saving Protection rewrites the whole rule set, **any Anti-Vanity-Change configuration is silently removed the next time you save this page**. If you rely on it, be aware that touching Protection settings will disable it. For a few rules — banning, kicking, channel creation and role creation — counts are tracked **per person rather than per server**. If the same moderator is active in two servers that share a bot process, their actions can count toward one another. It makes those rules trigger *earlier* than configured, never later, so it fails safe — but a surprising trigger may have this cause. ## A recommended baseline Without one you will not know Protection acted. Channel deletion, role deletion and banning cause the most damage and cannot be undone. Adding a malicious bot is the fastest way to destroy a server. Prefer a role-based override to a whitelist entry. ## Related Defends the door against mass joins. Control who can change these settings.