Read Discord command permissions and app context, then change them with approval
Connect Discord and Luumen can read the things that decide who can run what: application command permissions per guild, the batch view across every command, your bot's own guild member record, and the OAuth2 authorization behind it. When a permission needs to change, Luumen shows the edit first and applies it after you approve.
23 tools: 20 read, 3 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Discord run looks like inside Luumen.
Authorize once with OAuth 2.0. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — delete user application role connection, edit application command permissions, update user application role connection — is shown as a plan and requires approval by default, including the 1 action classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Discord — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Connect in minutes. Every action scoped, approved, and audited from day one.