Test Discord Mention and Thread Boundaries in Hermes Agent
A Discord mention controls when Hermes joins a conversation. User and channel authorization control who can invoke it and where. Verify both on a private test server before relying on either for a team bot.
- Private channel
- Mention and access checks
- Thread response
Set up a private routing experiment
Create a test bot using the setup in the official Discord integration guide. Give it access to a single private guild channel and avoid administrator permissions. Use a test Hermes profile with harmless tools and no production integrations. Store the bot token in the profile's secret environment configuration. Use the documented user and channel settings with your test IDs. Do not turn on allow-all switches. Check the authorization precedence in the docs for your installed release, since a scoped channel or role can affect user authorization.
For the behavioral test, set the following in the profile environment, then restart the test gateway. Verify no inherited overrides change routing.
DISCORD_REQUIRE_MENTION=true
DISCORD_AUTO_THREAD=true
DISCORD_THREAD_REQUIRE_MENTION=true
Run the matrix
Use an allowed user in the private channel. First send an ordinary line with no mention and expect no response. Then mention the bot with a single harmless question. Expect an auto-created thread if the bot has permission to create it. In that thread, send a plain follow-up and check that explicit mention policy still applies. Repeat with a mention. Finally use a test account that should be denied and inspect the behavior without any model request or external action.
Keep a log of test case, channel type, sender role and observed reply. Separate a missing platform permission from a policy decision. An OAuth install or Discord permissions issue may stop the bot from reading a message or making a thread at all. A policy denial can occur even when the message reached the gateway.
Do mention rules automatically protect direct messages? Channel mention behavior and direct-message authorization have different settings. Test direct messages independently if the bot is reachable there.
Why does the bot respond without a mention in one channel? Check configured free-response channels and environment precedence. Clear the exception in the test profile to measure the baseline.
References
Official Hermes Agent documentation · ASP.NET PB on MCP tools and resources
Comments
Post a Comment