> For the complete documentation index, see [llms.txt](/llms.txt).

# Trading modes

Trading modes apply to server-wallet only. During `mm init`, you are prompted to choose a trading mode.

## Guard Mode vs Beast Mode[​](#guard-mode-vs-beast-mode "Direct link to Guard Mode vs Beast Mode")

Guard Mode enforces all of your policies and asks for approval on anything outside them.

Beast Mode is for power users who want fewer interruptions. It still blocks and surfaces dangerous transactions.

info

We recommend **Guard Mode** for most users.

## Comparison[​](#comparison "Direct link to Comparison")

### Guardrails[​](#guardrails "Direct link to Guardrails")

Policies enforced automatically before a transaction can proceed.

| Guardrail                      | Guard Mode | Beast Mode |
| ------------------------------ | ---------- | ---------- |
| Threat scanning                | ✓          | ✓          |
| Network allowlist              | ✓          | —          |
| Address allowlist              | ✓          | —          |
| Token recipient allowlist      | ✓          | —          |
| Rolling 24-hour outflow limit* | ✓          | —          |

In Guard Mode, untrusted contracts, networks, and recipients are caught by your allowlists. In Beast Mode there are no allowlists.

### Requires 2FA approval[​](#requires-2fa-approval "Direct link to Requires 2FA approval")

Transactions that pause the job until you approve or reject them.

| Condition                        | Guard Mode | Beast Mode |
| -------------------------------- | ---------- | ---------- |
| Malicious transactions           | ✓          | ✓          |
| Risky contracts                  | ✓          | ✓          |
| Anything outside your allowlists | ✓          | —          |
| Raising your outflow limit       | ✓          | —          |

In Beast Mode, only malicious and risky transactions trigger approval.

note

See [Outflow policy](/agent-wallet/reference/outflow-policy/) for how outflows are tracked.

## Set your trading mode[​](#set-your-trading-mode "Direct link to Set your trading mode")

Set the mode with the `--mode` flag, or pick it at the interactive prompt:

```
mm init --mode guard   # or --mode beast

```

## How 2FA approval works[​](#how-2fa-approval-works "Direct link to How 2FA approval works")

When a transaction needs approval, the CLI pauses the job until you approve or reject it. The agent cannot proceed on a flagged or policy-violating transaction without your response.

Your sign-in method during `mm login` determines where the approval request is sent:

| Sign-in method              | Approval channel                  |
| --------------------------- | --------------------------------- |
| MetaMask Mobile (QR code)** | MetaMask Mobile push notification |
| Google or email             | Email link                        |

** QR code sign-in (`mm login qr`) is coming soon.

## Switch modes[​](#switch-modes "Direct link to Switch modes")

Re-run `mm init` with a different `--mode` value to change modes. Confirm your active configuration with:

```
mm init show

```

## Outflow policy[​](#outflow-policy "Direct link to Outflow policy")

Guard Mode enforces a rolling 24-hour outflow limit on server-wallet outgoing transfers. You're prompted to set the limit on your first transaction, or when a transaction would exceed your current limit. If a transaction would exceed the limit, or you request a higher limit, the CLI requires 2-factor authentication approval before the transaction proceeds.

See [Outflow policy](/agent-wallet/reference/outflow-policy/) for how outflows are calculated, what counts toward the limit, and known limitations.