List all server operators from ops.json.
AI agents call list_ops to retrieve information from Minecraft Server MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple data retrieval operation—reading the ops.json file to enumerate server operators. It has no side effects, does not modify state, and does not execute commands or trigger external operations. While the Minecraft server context involves administrative functions, this specific tool is limited to reading existing configuration data, making it a Read category risk with low severity.
From the tool's definition Tool name 'list_ops' and description 'List all server operators from ops.json' indicate a read-only query operation that retrieves and displays existing operator data without modification or execution.
Attacks that exploit this kind of access
List all server operators from ops.json. It is categorised as a Read tool in the Minecraft Server MCP MCP Server, which means it retrieves data without modifying state.
Register the Minecraft Server MCP server in PolicyLayer and add a rule for list_ops: 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.
list_ops 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 list_ops 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 list_ops. 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.
list_ops is provided by the Minecraft Server MCP server (tamo2918/minecraft-server-mcp). 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 →