Webhook Guard

Close the webhook loophole that bypasses member checks.

Why it matters

A webhook posts messages in your channel without being a member of the server, so it bypasses every check applied to members. Anyone who creates a webhook in a channel can flood it with links or ads from outside the server entirely. This guard closes the hole from three sides: blocking untrusted creation, screening messages, and sweeping the unknown.

The webhook list

The creation gate

Message screening

Offline sweep

Trust and exemptions

Tips

A webhook posts in your channel without being a member, bypassing every check applied to members: no role is examined, no account can be banned, and no membership guard sees it. Anyone who creates one can flood your channel with links or ads from entirely outside the server.

The guard closes it from three sides. The creation gate deletes any webhook made by an untrusted member and punishes the creator. Message screening reads what a webhook posts and blocks invite links and phishing-shaped links, and catches flooding, heavy mentions, and cross-posting across channels. And the offline sweep hunts for webhooks that appeared while the bot was down.

The guard page shows every webhook in the server in one table: which are trusted, which the bot created itself, and which appeared while it was offline. Alongside it sits an event log showing what was deleted and what was flagged, plus instant delete and add-to-trusted buttons.

A practical note before enabling it: add the webhooks of your legitimate tools to the trusted list first, or they get deleted and the services relying on them break. And start with flag rather than immediate delete so you can see what it catches.