mc_execute_command · Mc Rcon MCP: Risk & Policy

WHAT IT DOES

What mc_execute_command does on Mc Rcon

AI agents invoke mc_execute_command to trigger actions in Mc Rcon. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why mc_execute_command needs a policy

This tool allows execution of arbitrary Minecraft commands on a server via RCON protocol. While some Minecraft commands are informational (Read), many alter server state, affect gameplay, or trigger external operations (granting ops, managing whitelists, stopping server, etc.). The tool itself is an execution primitive with side effects dependent on the command argument.

From the tool's definition Tool description states 'Execute a Minecraft command on the server via RCON'. The server description confirms it 'Enables Minecraft server management via RCON: execute commands' — this is explicitly an execution primitive that runs arbitrary commands on a…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

mc_execute_command Rate-limited

mc_execute_command stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "mc_execute_command": {
      "limits": [
        {
          "counter": "mc_execute_command_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Mc Rcon, so you can run agents against it safely.

FAQ

Questions about mc_execute_command

What does the mc_execute_command tool do? +

Execute a Minecraft command on the server via RCON. It is categorised as a Execute tool in the Mc Rcon MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on mc_execute_command? +

Register the Mc Rcon MCP server in PolicyLayer and add a rule for mc_execute_command: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Mc Rcon. Nothing to install.

What risk level is mc_execute_command? +

mc_execute_command is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit mc_execute_command? +

Yes. Add a rate_limit block to the mc_execute_command rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block mc_execute_command completely? +

Set action: deny in the PolicyLayer policy for mc_execute_command. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides mc_execute_command? +

mc_execute_command is provided by the Mc Rcon MCP server (pedxyuyuko/mc-rcon-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.