What the MineOps agent can and cannot do
The agent connects out, runs as its own unprivileged user, installs only signed releases and changes nothing until you allow it. Here is everything it does and what MineOps keeps.
Installing anything on the machine that runs your worlds deserves a careful look. This page says exactly what the MineOps agent does, and what it cannot do.
It only connects out
The agent opens one connection out to MineOps over HTTPS and never listens for connections. You open no ports, and nothing on the internet can reach the agent directly.
It runs with as little access as possible
- On Linux it runs as its own unprivileged user,
mineops-agent, in a hardened systemd service, and reads only the folders it is given through group permissions. - On a Mac it runs as you, for the server folder the setup found.
- Servers that Docker runs stay monitored only, unless the machine's owner runs the agent's allow-Docker command once. That gives the agent root-equivalent access, so MineOps never does it for you.
Nothing changes until you allow it
Starting and stopping, moderation, the console, settings, backups and restores are each off for a server until the machine's owner allows them. Every operation is a specific, checked action, such as “restart this server” or “kick this player”: there is no way to run arbitrary commands on your machine through MineOps. Console commands go only to the Minecraft console, only for the organization's owners, and only where allowed. Every operation is recorded in the audit log with who asked for it.
It proves who it is and installs only signed releases
- The agent makes its own key on your machine; the key never leaves it. You approve a new machine by matching a six-digit code, and you can revoke it at any time.
- Releases are signed. The installer is checked against the release's signed checksum before it runs, and the agent installs only updates signed with MineOps's release key, when you start them.
What MineOps keeps
- Your servers' status, settings and metrics, operation history and your organization's audit log.
- Player names and play times for player history, never IP addresses or chat.
- Live log lines while you watch the console, kept an hour at most. Passwords, token-like values and IP addresses are removed on your machine before they are sent.
- The agent's own warnings and errors, redacted the same way, for 30 days.
- Backup sizes and checksums, never your worlds or the backups themselves.
Your team signs in with a password or Google, with two-step sign-in available for every account. MineOps support can see a summary of your organization only through a time-limited access grant with a written reason, and every grant, view and change appears in your audit log. Owners can export everything, or delete the organization. The privacy policy has the full details.
Removing it
On the machine's Agent setup, choose Uninstall agent. The agent removes itself and its permissions; your Minecraft servers and worlds stay where they are.