Tool
Is this bot asking for too much?
Paste a bot's invite link or permission number. You'll see every permission it requests, how risky each one is, and what it could do if the bot were compromised.
Everything runs in your browser. Nothing you paste is sent anywhere.
Verdict
Broad
Several powerful permissions. Normal for moderation or setup bots, but make sure every one is used.
268454914
0x10004C02
Critical risk
0
High risk
2
Medium risk
0
Low risk
3
Findings
Role position matters
Manage Roles only affects roles below the bot's highest role. Server owners should keep the bot's role below moderator roles.
2 permissions affected by server 2FA
In servers that require 2FA for moderation, the bot owner's account needs 2FA enabled for Kick Members, Manage Roles to work.
This looks like a verification bot. Its sensitive permissions match what that kind of bot needs.
Compare with the example5 permissions requested
Lets the bot remove members from the server. They can rejoin with a new invite. Only members whose highest role is below the bot's highest role can be kicked.
If the token leaks: A leaked token can be used to kick every member below the bot's role in seconds.
Lets the bot create, edit, assign and delete roles below its own highest role, and edit channel permission overwrites. Used by reaction-role, verification and leveling bots.
If the token leaks: A leaked token can hand out any role below the bot's, including moderator roles, and edit channel overwrites to expose private channels.
Lets the bot see channels. Almost every bot needs this, and server owners can still hide specific channels with overwrites.
Lets the bot post messages. Note that replying to slash commands does not need this permission.
Lets links the bot posts show a preview, and is required for bots that send rich embeds.