Manage the server whitelist.
AI agents use whitelist_manage to create or update resources in Minecraft Server MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Minecraft Server MCP environment.
Whitelist management allows adding or removing players from access control lists, which modifies server state reversibly. Players can be re-added to the whitelist if removed. While this affects server access and player experience, it is not destructive (data loss), financial, or code execution.
From the tool's definition Tool name 'whitelist_manage' and description 'Manage the server whitelist' indicates creation and modification of whitelist entries. Sibling tools like 'ban_player', 'deop_player', and 'execute_command' confirm this is an administrative modification tool.
Attacks that exploit this kind of access
Manage the server whitelist. It is categorised as a Write tool in the Minecraft Server MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Minecraft Server MCP server in PolicyLayer and add a rule for whitelist_manage: 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.
whitelist_manage is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the whitelist_manage 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 whitelist_manage. 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.
whitelist_manage 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 →