minecraft-server-admin

Execute Minecraft Java Edition admin commands through the RCON remote console. Use for player moderation, whitelist management, item/state commands, world ru...

Security Scan

The skill's code, install, and environment needs match its stated purpose (RCON-based Minecraft admin) with only minor, explainable inconsistencies to review before install.

Purpose & Capability

The skill requires node and the expected RCON env vars (MC_RCON_HOST, MC_RCON_PORT, MC_RCON_PASSWORD) which are appropriate for a remote RCON admin tool. Minor inconsistency: the install spec declares the npm package 'rcon-client', but the included scripts implement the RCON protocol directly using Node's net/Buffer API and do not require('rcon-client'). This is likely harmless (an unused dependency) but worth confirming.

Instruction Scope

SKILL.md stays within its stated scope: it sends RCON commands and (optionally) reads the server log file when MC_SERVER_LOG is set. It requires confirmations for destructive/high-privilege commands. The instructions also request appending audit entries to the agent's OpenClaw Memory after operations — this is appropriate for auditability but means command history/results will be stored in agent memory (review retention/privacy settings).

Install Mechanism

Installation is a standard Node dependency (rcon-client) from the npm ecosystem — a low/moderate risk install mechanism. No downloads from arbitrary URLs or extract/install-from-remote-archive steps are present.

Credentials

Required environment variables (MC_RCON_HOST, MC_RCON_PORT, MC_RCON_PASSWORD) are directly relevant and proportionate to RCON connectivity. An optional MC_SERVER_LOG is referenced for log analysis (not listed as required). No unrelated secrets or other service credentials are requested.

Persistence & Privilege

The skill is not set to always:true and does not request system-wide modifications. It does ask the agent to append audit logs to OpenClaw Memory (its own agent memory) after actions, which is normal for audit purposes. There is no evidence it modifies other skills or global configuration.

Assessment

This skill appears to implement exactly what it claims: an RCON-based remote admin for Minecraft Java servers. Before installing: 1) Ensure you only point MC_RCON_HOST/PORT/PASSWORD at servers you control (RCON grants powerful admin access). 2) Review OpenClaw memory/audit retention settings because the skill will append executed commands/results to agent memory. 3) Confirm whether the declared npm dependency 'rcon-client' is intentional or unused (the included rcon.js implements RCON itself); an unused dependency is usually benign but worth checking. 4) If you set MC_SERVER_LOG, restrict its path to the server logs you intend to expose; the analyzer will read that file. If those points are acceptable, the skill is coherent with low risk.

Scope: This skill is your in-game remote control for a Minecraft Java server. It sends commands through the RCON protocol to manage players, world state, and server communication in real time. It intentionally excludes server-infrastructure operations such as process lifecycle management, filesystem backups, plugin jar installation, and continuous uptime monitoring; use a dedicated PaperMC ops skill for those. This skill does NOT require minecraft-bridge — it communicates directly with the server's admin console over a separate TCP connection.

Architecture:

OpenClaw → RCON TCP (port 25575) → Minecraft Server Console

---

Prerequisites

Enable RCON on the Server

Edit server.properties:

enable-rcon=true
rcon.port=25575
rcon.password=STRONG_PASSWORD_HERE
broadcast-rcon-to-ops=false

Restart server after changing these values.

Environment Variables

MC_RCON_HOST=localhost        # Server IP or hostname
MC_RCON_PORT=25575            # RCON port (must match server.properties)
MC_RCON_PASSWORD=yourpassword # RCON password (must match server.properties)
MC_SERVER_LOG=/path/to/server/logs/latest.log  # optional, for log analysis

Verify Connection

node ~/.openclaw/skills/minecraft-server-admin/scripts/rcon.js "list"
# Expected: "There are N of a max of M players online: ..."

---

Operation Categories

PLAYER MANAGEMENT

For any player-related command, use: scripts/rcon.js "<command>"

Listing & Checking

• "who is online" → /list → parse player count and names
• "is [player] online" → /list then check if name appears

Access Control ⚠️ Requires confirmation before executing:

• kick: /kick <player> [reason]
• temp ban: /ban <player> [reason] + calendar note
• permanent ban: /ban <player> [reason]
• ban IP: /ban-ip <player|ip> [reason]
• unban: /pardon <player> or /pardon-ip <ip>
• whitelist add: /whitelist add <player>
• whitelist remove: /whitelist remove <player>
• op player: /op <player> ⚠️ HIGH PRIVILEGE — always confirm
• deop player: /deop <player>

Item & State Management

• give items: /give <player> <item_id> [count]
• clear inventory: /clear <player> [item] [count]
• set gamemode: /gamemode <survival|creative|adventure|spectator> <player>
• teleport: /tp <player> <x> <y> <z> or /tp <player> <target_player>
• set health/hunger: /effect give <player> minecraft:regeneration ...
• heal player: /effect give <player> minecraft:instant_health 1 10

WORLD MANAGEMENT

Time & Weather

• day: /time set day
• night: /time set midnight
• sunrise: /time set 0
• clear weather: /weather clear [seconds]
• rain: /weather rain [seconds]
• thunder: /weather thunder [seconds]

World State

• save world: /save-all (always do before maintenance)
• save-off (for backup): /save-off then backup then /save-on
• change difficulty: /difficulty <peaceful|easy|normal|hard>
• set game rule: /gamerule <rule> <value>
  • Examples: keepInventory true, doDaylightCycle false, doFireTick false
• find structure: /locate structure minecraft:<structure_name>
• fill area: /fill <x1 y1 z1> <x2 y2 z2> <block> ⚠️ Confirm range before running

Entity Management

• kill all mobs: /kill @e[type=!player] ⚠️ Confirm — kills all non-players
• kill specific type: /kill @e[type=minecraft:zombie]
• remove dropped items: /kill @e[type=minecraft:item]

BROADCAST & COMMUNICATION

• server message: /say <message> (prefixed with [Server])
• title on screen: /title @a title {"text":"<msg>","color":"gold","bold":true}
• subtitle: /title @a subtitle {"text":"<msg>"}
• private message: /msg <player> <message>
• actionbar: /title @a actionbar {"text":"<msg>"}

PERFORMANCE MONITORING

When asked about server performance:

1. Execute /list → check player count
2. Read MC_SERVER_LOG file (last 200 lines) if path set
3. Look for patterns in references/log-patterns.md
4. Report: TPS warnings, error frequency, player activity spikes

---

Safety Protocols

Confirmation required for all destructive/high-privilege commands:

⚠️  Dangerous Operation
Command: /ban SomePlayer griefing and harassment
Server:  ${MC_RCON_HOST}:${MC_RCON_PORT}
Effect:  Permanently bans SomePlayer from server

Type 'confirm' to proceed, or 'cancel' to abort.

Operations requiring confirmation:

• ban, ban-ip — permanent account restriction
• op — grants admin privileges
• fill — large area modification
• kill @e — entity mass-removal
• stop — server shutdown
• save-off — pauses auto-save (dangerous if forgotten)

Audit logging: After each operation, append to OpenClaw Memory:

## Server Admin Log [ISO timestamp]
- Command: /ban PlayerX "repeated griefing"
- Executed by: [OpenClaw user]
- Result: success

---

Response Formatting

Player List (/list response)

Parse and present as:

👥 Players Online (3/20):
  • Steve — [show coords if available]
  • Alex
  • Notch

Kicked/Banned confirmation

✅ Done: PlayerX has been banned
   Reason: griefing
   Effective immediately
   To undo: /pardon PlayerX

Error Responses

• Connection refused → check RCON settings, server running?
• Authentication failure → wrong MC_RCON_PASSWORD
• Command returned empty → server may not have recognized command (check version)

---

Log Analysis

When user asks about server health or player history:

1. Check MC_SERVER_LOG is set and file exists
2. Read the last N lines: tail -500 <log_file>
3. Apply patterns from references/log-patterns.md
4. Summarize findings:

📊 Server Log Summary (last 2 hours)
  Player logins: 14
  Player logouts: 12 (2 still online)
  Errors/Warnings: 3
    - [15:42] Can't keep up! Running 2500ms behind
    - [16:10] Saving chunks for level 'world'
  Suspicious activity: none detected

Additional Resources

• references/commands.md — All vanilla commands with syntax and permission level
• references/log-patterns.md — Common log patterns and what they mean
• scripts/rcon.js — RCON client (used by all commands above)
• scripts/log-analyzer.js — Log parsing utilities