Change a player
AI agents invoke set_gamemode 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.
Changing a player's game mode (e.g., survival, creative, spectator) is a server-side operation that modifies runtime state for a specific player. It is not purely a data write (it triggers server-side behavior changes) and not destructive or financial. The description is truncated, lowering confidence slightly.
From the tool's definition 'set_gamemode' and 'Change a player' — the description is truncated/uninformative, but the tool name implies changing a player's game mode on the server, which is an external operation with immediate effect on gameplay
Attacks that exploit this kind of access
Change a player. 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 set_gamemode: 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.
set_gamemode 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 set_gamemode 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 set_gamemode. 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.
set_gamemode 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 →