Send commands to the Minecraft server
AI agents invoke send_command to trigger actions in Minecraft Server MCP. 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.
This tool sends arbitrary commands to a Minecraft server, which can trigger a wide range of server-side operations including kicking/banning players, modifying the world, granting permissions, stopping the server, or executing operator-level commands. The blast radius is high because misuse could disrupt an active server and its players, cause irreversible world changes, or escalate privileges.
From the tool's definition 'Send commands to the Minecraft server' — executes arbitrary commands on a live game server
Attacks that exploit this kind of access
Send commands to the Minecraft server. It is categorised as a Execute tool in the Minecraft Server MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Minecraft Server MCP server in PolicyLayer and add a rule for send_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 Minecraft Server MCP. Nothing to install.
send_command is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the send_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.
Set action: deny in the PolicyLayer policy for send_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.
send_command is provided by the Minecraft Server MCP server (ver-zhzh/mcp-for-minecraft-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →