How actions work

MCTotem can apply approved fixes to your server, not just describe them. Actions are part of the paid plan and require the agent plugin. Everything on this page sits on top of the safety model; read that page if your first question is "why would I let a bot touch my server".

The lifecycle

1. A diagnosis proposes an action alongside its fix steps.
2. The action waits for approval (unless you switched its class to auto-run).
3. You approve from the dashboard's Action center, or from Discord with a button or /approve.
4. The worker signs the action and dispatches it to your agent plugin, which verifies the signature and executes it.
5. The result lands in the audit log, and where it makes sense, the test player verifies the fix by joining.

Every action expires 10 minutes after signing. An approval you forgot about overnight cannot fire in the morning.

Action classes

You enable each class separately in the server's Action center. The full reference with limits and the hardcoded denylist is at action classes.

• Config edits: applied as a diff, with an automatic backup taken first and one-click rollback.
• Console commands: only commands on an allowlist you define, and never anything on the hardcoded denylist.
• Plugin toggle: enable or disable a plugin. Can never disable the MCTotem agent itself.
• Restart request: asks for a restart; it never issues a console stop itself.

Approval modes

Each class is approve-each by default: every action waits for a human. Once you trust a class, you can switch it to auto-run. The class still obeys the denylist, the signature check, the kill switch and the audit log; auto-run only removes the waiting step. You can switch a class back at any time.

Related

• The safety model
• Action classes and denylist
• Discord bot