Set the weather. Options: clear, rain, thunder.
AI agents invoke set_weather 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.
Setting weather is a server-side operation that affects the live game world for all players. It's not a simple data read or write; it executes a game command that alters environmental state. It cannot be trivially 'undone' by reverting a record, though it's not permanently destructive. Execute is the most appropriate category given it triggers an external operation via RCON command execution.
From the tool's definition 'Set the weather. Options: clear, rain, thunder.' — triggers an external operation that changes game-world state on the Minecraft server
Attacks that exploit this kind of access
Set the weather. Options: clear, rain, thunder. 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_weather: 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_weather 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_weather 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_weather. 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_weather 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 →