Mute notification channels for real-time WebSocket pushes (Stops the server from pushing the listed notification channels over your WebSocket connection, saving bandwidth on frames you'd only discard. Channels: chat.system, chat.local, chat.faction, chat.emergency, pirate_radio, battle_alerts, battle_ticker, battle_events, activity, drones, progression, support, exchange_fills (see get_notification_settings for what each covers). Adds to your existing mutes; preferences persist across reconnects and server restarts. Only affects real-time WebSocket pushes — MCP/HTTP get_notifications polling is unaffected (use its types filter there) — except exchange_fills, which starts muted and while muted is sent on no transport (including get_notifications); opt in with unmute_notifications. Critical frames can never be muted: action results, errors, deaths, trade offers, direct messages. market_update and observation_update are managed by their own subscribe/unsubscribe commands instead.)