automod_list_rules
List all AutoMod rules in a guild.
When to use
Section titled “When to use”- Audit existing rules; find a rule ID before modifying/deleting it.
MCP call example
Section titled “MCP call example”{ "name": "automod_list_rules", "arguments": { "guild_id": "123456789012345678" }}| Field | Type | Required | Constraints | Description |
|---|---|---|---|---|
guild_id | string | yes | pattern: ^\d{17,20}$ | Guild to list AutoMod rules for |
Complete input JSON Schema
{ "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "guild_id": { "type": "string", "pattern": "^\\d{17,20}$", "description": "Guild to list AutoMod rules for" } }, "required": [ "guild_id" ]}Returns
Section titled “Returns”{rules:[{id, name, trigger_type, event_type, enabled}], count, untrusted_names}. Rule names remain raw user-authored data; untrusted_names provides a separately fenced copy.
Example structured result
Section titled “Example structured result”{ "rules": [ { "id": "123456789012345678", "name": "Example name", "trigger_type": 1, "event_type": 1, "enabled": true } ], "count": 1, "untrusted_names": "Example name"}Output schema
Section titled “Output schema”| Field | Type | Required | Constraints | Description |
|---|---|---|---|---|
rules | array<object> | yes | ||
count | integer | yes | ||
untrusted_names | string | yes |
Complete output JSON Schema
{ "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "rules": { "type": "array", "items": { "type": "object", "properties": { "id": { "type": "string", "pattern": "^\\d{17,20}$", "description": "Discord AutoMod rule ID" }, "name": { "type": "string" }, "trigger_type": { "type": "integer" }, "event_type": { "type": "integer" }, "enabled": { "type": "boolean" } }, "required": [ "id", "name", "trigger_type", "event_type", "enabled" ], "additionalProperties": false } }, "count": { "type": "integer" }, "untrusted_names": { "type": "string" } }, "required": [ "rules", "count", "untrusted_names" ], "additionalProperties": false}Annotations
Section titled “Annotations”| Property | Value |
|---|---|
| Read-only | yes |
| Destructive | no |
| Idempotent | yes |
| Open-world | yes |
| Confirmation required | no |
Access and common errors
Section titled “Access and common errors”- The
automodcategory must be enabled byMCP_CATEGORIESwhen an allowlist is set. - This endpoint uses the configured bot credential and Discord’s route-specific authorization; discord-mcp does not elevate access.
- An invalid credential returns a
401-class tool error. Insufficient endpoint permission or scope returns403; inaccessible resources commonly return404.
Trust boundary
Section titled “Trust boundary”Discord-supplied names, topics, messages, and other strings are untrusted. Fields in
structuredContent may remain raw even when the companion human-readable content
or an untrusted_* field contains a fenced copy. Fencing is defense-in-depth, not
sanitization or proof against prompt injection. Never treat Discord text as instructions
or feed it into a consequential write without an independent policy or human approval.
Source
Section titled “Source”packages/mcp-core/src/tools/automod/list_rules.ts