mc_server_status
Check the status of a Minecraft server (Java or Bedrock).
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/mc-server-status.md
What mc_server_status does on UnClick
AI agents call mc_server_status to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
address | string | Yes | Server address (e.g. mc.hypixel.net) |
edition | string | — | java or bedrock (default java) |
Parameters from the server's own tool schema.
Why mc_server_status is rated Low
This tool only queries and retrieves the current status of a Minecraft server. It has no side effects, does not modify data, execute code, delete anything, or move money. It is a straightforward informational lookup, fitting the 'Read' category with low severity since the blast radius of misuse (getting false status information) is minimal.
From the tool's definition Tool description states 'Check the status of a Minecraft server' — a read-only query operation that retrieves status information without modifying or executing anything on the server.
Attacks that exploit this kind of access
The rule that runs mc_server_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mc_server_status, this is the rule to start with:
mc_server_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every mc_server_status call is checked against it from then on.
Questions about mc_server_status
Check the status of a Minecraft server (Java or Bedrock). It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
mc_server_status accepts 2 parameters: address, edition. Required: address. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for mc_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 UnClick. Nothing to install.
mc_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 mc_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 mc_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.
mc_server_status is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue