Mod Guard

Mod Guard protects your server from your own moderators going rogue — a hijacked account, a rage-ban, or someone trying to wreck the server. It counts what each moderator does and steps in when it's too much, too fast. It is free.

Alpha — new; tell us if something looks off.

How it works

CloudMod counts, per moderator and per action, how often they act inside a rolling window (default 10 minutes). When someone goes over the limit, CloudMod posts an alert to the Mod Guard logging category and — if you chose it — takes their moderator roles away.

Counted actions:

• Bans (a mass-ban counts every member in it)
• Kicks
• Timeouts (setting one — lifting one doesn't count)
• Warns (/warn)
• Deletions of channels and roles

Defaults: 3 bans · 5 kicks · 8 timeouts · 10 warns · 4 deletions per 10 minutes. Set a limit to 0 to switch that action off.

Settings

Enable Mod Guard under All features, then open Mod Guard in the sidebar:

• Time window (minutes) — 1–1440. Default 10.
• Limits — 0–100 per action. A moderator going over the number triggers the guard; reaching it exactly does not.
• Exempt roles — members with one of these roles (Co-Owner, head admins …) are never limited or counted. Up to 25 roles.
• Limits per role — give a role its own limits, e.g. stricter ones for new mods. A moderator with several of these roles gets the most generous limit (0 = no limit). Everyone else uses the general limits.
• When a limit is exceeded — Remove moderator roles (default) or Only alert me.

What "remove moderator roles" does

It removes the moderator's roles that carry moderation power (Administrator, Kick, Ban, Timeout, Manage Roles / Channels / Server). Roles without such powers, like cosmetic ones, stay. The alert lists every role that was removed, so you can give them back once you've checked what happened.

Limits you should know

• The guard acts after the limit is exceeded — the action over the limit still happens.
• CloudMod can only remove roles below its own highest role and not roles managed by an integration. Keep CloudMod's role high. If it can't remove a role, the alert says so.
• The server owner and bots (CloudMod itself and other bots) are never touched; for the owner you get an alert only.
• Needs View Audit Log (to see who banned or kicked) and Manage Roles (to remove roles). /checkperms shows if an older invite lacks them.
• Bans are not undone automatically.
• Counting lives in memory: a bot restart clears it.

Where the alerts go

Alerts use the Mod Guard logging category. Route it to a channel your team watches on the Logging page — or hit Auto-create channels to get a dedicated mod-guard channel. The admin role is pinged (at most once per hour). If you switch the category off, the guard still removes roles, but no alert is posted.