Approvals & Requests

The Requests tab is the approval surface for MCP-driven actions.

When an agent asks MUTX to do something sensitive without an SLK, the TUI stores the request locally and waits for operator input.

What shows up here

• wallet list exposure requests
• wallet details and balance requests
• receive address requests
• SOL send requests
• swap requests
• address book list and add requests
• SLK creation requests

Approval flow

1. The MCP client calls a tool
2. mutx-mcp forwards the request to mutx-tui
3. The request appears in the TUI
4. You approve with y or deny with n
5. The MCP client receives the result

WalletConnect is separate

WalletConnect does not use the Requests queue for session proposals. Pairings, proposals, and live sessions are handled from the DApps tab.

Request history

Approved and denied requests remain useful as an audit trail:

• d removes a request from the visible history
• e copies the explorer URL when one exists

For deeper troubleshooting, use the Logs tab or the mutx-tui logs export command.