Skip to main content
The Remote Command system lets you send commands to any registered Botify PC via the botify_commands MongoDB collection — no direct network connection to the target PC required.

How It Works

1

Insert Command

A command document is inserted into the botify_commands MongoDB collection, targeting a specific PC by target_pc name.
2

Node Polls

The target Botify instance polls botify_commands every few seconds and finds the pending command.
3

Auth Verification

The node verifies the auth_token matches its command_token. If it doesn’t match, the command is silently rejected.
4

Execution

The command is executed on the target PC.
5

Audit Log

Result is written to botify_command_history. The command document is removed from the queue.
All commands require a valid auth_token matching the target node’s command_token. Invalid tokens are silently rejected and logged.

Command Reference

Engine Control

Account Management

Diagnostics

UI Control


Command Document Format


Example Commands


system_stats Response


Audit History

After execution, every command is logged in botify_command_history:

Security

  • auth_token is a 32-byte random hex string generated on first run, stored in botify_nodes
  • Commands without a matching token are silently rejected — no error is returned to prevent enumeration
  • The lock command disables all UI controls on the target PC — useful for preventing interference during automated runs
  • owner_id verification is optional but recommended for an additional layer of access control