How to Protect Your Discord Server From Raids
Published 13 Nov 2026
Also available in: Português · Español · Deutsch · Français
A raid is a coordinated wave of accounts joining a server to flood it with spam, slurs, scam links or mass pings. It usually lasts minutes, but the cleanup and the damage to trust can last much longer. The good news: most raids rely on the same weaknesses, and a few settings close most of them.
This guide covers prevention (what to configure today), detection (how to notice early) and response (what to do in the first five minutes).
Layer 1: Discord's own settings
Start with what Discord gives you for free. These settings live in Server Settings, mostly under Safety Setup or Moderation.
Verification level
| Level | Requirement before chatting |
|---|---|
| None | Nothing |
| Low | Verified email on the account |
| Medium | Registered on Discord for more than 5 minutes |
| High | Member of the server for more than 10 minutes |
| Highest | Verified phone number |
For most public servers, Medium is a sensible default. During an active raid, temporarily raising it to High buys time, since new joiners cannot speak for ten minutes. The details are on Discord's support site.
Other native protections
- Discord AutoMod: built-in filters for keywords, spam and mention spam. Turn on what fits your server.
- Require 2FA for moderation actions: protects you if a moderator account is compromised.
- Pause invites: Discord lets you temporarily stop new joins through invites; check the support site for where it appears in your current client.
- Permission hygiene: make sure @everyone cannot mention @everyone/@here, and decide whether regular members should be able to create invites.
Layer 2: A bot's AutoMod as a second net
Native filters are a good base. A bot's AutoMod adds rules that are easy to tune per server. In MagnificBot, the AutoMod module covers:
- Spam: more than a set number of messages in a set number of seconds (by default, 6 messages in 5 seconds).
- Discord invites: blocked by default.
- Links: optional, with a list of allowed domains.
- Mass mentions: maximum mentions per message (8 by default).
- Caps: percentage of capital letters on longer messages.
- Banned words: up to 200 words or phrases.
- Exempt roles and channels, so staff and specific channels are not affected.
For each violation you choose the response: delete, delete and warn, or delete and timeout (you set the timeout length). Violations are reported to a log channel.
Raid-ready tip: keep a stricter configuration in mind. During an attack, switching the action from "delete and warn" to "delete and timeout" turns every spam message into an instant mute.
Layer 3: Account-age gates
Raid accounts are often created minutes or hours before the attack. A gate based on account age stops them from reaching your main channels, even if they get past Discord's verification level.
With MagnificBot's Automations module:
- Trigger: member joins.
- Condition: account older than (days), for example 7.
- Action: add role "Member".
Set your chat channels to require "Member". New accounts only see your rules, help and welcome channels, so a raid of fresh accounts has nowhere to post. The join log shows each new member's account age, which helps you spot a wave of new accounts quickly.
Layer 4: Timeouts and escalation
Timeouts are the right tool in the heat of the moment: they silence someone for up to 28 days without removing them, and they are easy to reverse if you made a mistake. MagnificBot's moderation module adds:
/timeout,/kick,/banand temporary bans, all recorded as cases with notes.- Automatic escalation: after a set number of warnings, a timeout, kick or ban is applied.
- Actions taken by hand in Discord's own menus are also logged as cases, so your history stays complete.
The five-minute raid response plan
Write this down and pin it in your staff channel:
- Raise the verification level to High and pause invites if needed.
- Tighten AutoMod: set the action to delete and timeout, and lower the mention limit.
- Clean up:
/purgedeletes up to 100 recent messages at a time, optionally from a single user (Discord only allows bulk deletion of messages less than 14 days old). - Remove the raiders: ban the accounts involved; banning can also delete their recent messages.
- Review the logs: member joins with account age and moderation cases tell you who joined and when.
- Restore settings once things are calm, and post a short message to reassure members.
After the raid
- Check where the raiders came from: a leaked invite link? Replace it.
- Review which roles can mention @everyone or create invites.
- Give staff dashboard access by role (Admin, Moderator, Support, Designer, Viewer) so helpers can follow the logs without receiving extra Discord permissions.
Everything above is included in MagnificBot's free plan. For an overview of how it compares with other moderation bots, see our MEE6 vs Dyno vs Carl-bot vs MagnificBot comparison.
FAQ
What verification level should I use against raids?
Medium is a good everyday default. Raise it to High during an active raid so newcomers cannot chat for ten minutes.
Can a bot stop a raid completely?
No tool stops everything, but layered defences (verification level, AutoMod, account-age gates, fast timeouts) make raids short and easy to clean up.
How do I delete raid spam quickly?
Use /purge with an amount up to 100, optionally filtered by user, and ban the accounts involved.
Does MagnificBot need Administrator to moderate?
No. It asks for specific permissions when invited, not Administrator.
Prueba MagnificBot gratis
Todos los módulos incluidos y configurados desde un panel web. Sin tarjeta y sin fecha de caducidad.
Añadir a Discord — es gratis