Check if the Minecraft server is running and responsive.
AI agents call check_server_status to retrieve information from Minecraft Docker MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries the operational status of the Minecraft server. It performs no writes, deletions, code execution, or financial operations. It is purely informational retrieval with no blast radius if misused by an AI agent—the worst outcome would be receiving status information that could guide subsequent actions, but the tool itself cannot cause harm.
From the tool's definition Tool name 'check_server_status' and description 'Check if the Minecraft server is running and responsive' indicate a read-only query operation that retrieves server state without modification or side effects.
Documented attack patterns abuse exactly the kind of access check_server_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Minecraft Docker MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for check_server_status:
{
"version": "1",
"default": "deny",
"tools": {
"check_server_status": {}
}
}check_server_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check if the Minecraft server is running and responsive. It is categorised as a Read tool in the Minecraft Docker MCP MCP Server, which means it retrieves data without modifying state.
Register the Minecraft Docker MCP server in PolicyLayer and add a rule for check_server_status: 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 Docker MCP. Nothing to install.
check_server_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the check_server_status 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 check_server_status. 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.
check_server_status is provided by the Minecraft Docker MCP server (rgbkrk/rcon-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Minecraft Docker MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
6 Minecraft Docker MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.