Remote Commands
Sending remote commands to endpoint devices.
Overview
Remote commands let you control devices from the admin dashboard. Commands are queued on the server and picked up by agents during their next heartbeat or command poll.
Available Commands
| Command | Description | Requires |
|---|---|---|
| `lock` | Lock the device screen | — |
| `wipe` | Wipe agent data | `confirm: true` in payload |
| `restart_agent` | Restart the agent process | — |
| `update_policy` | Force immediate policy sync | — |
| `force_encrypt` | Enable disk encryption | — |
| `collect_status` | Request full status report | — |
| `enable_guard` | Enable a specific guard | Guard name |
| `disable_guard` | Disable a specific guard | Guard name |
| `set_message` | Display message on device | Message text |
| `run_scan` | Run compliance scan | — |
Command Lifecycle
Admin sends command → pending → delivered → executed/failed- pending — Command created, waiting for agent to poll
- delivered — Agent received the command
- executed — Agent successfully executed the command
- failed — Agent failed to execute (result includes error details)
Sending a Command
- Navigate to Devices → select a device
- Click Send Command
- Select the command type
- Add any required parameters
- Click Send
Platform-Specific Implementation
| Command | Windows | macOS |
|---|---|---|
| `lock` | `LockWorkStation` API | `pmset displaysleepnow` |
| `set_message` | `MessageBox` | `osascript display dialog` |
| `force_encrypt` | Enable BitLocker | Enable FileVault |
| `restart_agent` | `os.execv()` self-restart | `os.execv()` self-restart |
Security
- The
wipecommand requires explicitconfirm: truein the payload to prevent accidental data loss - Only
tenant_managerand above can send commands - All commands are logged in the audit trail