Add a player to the whitelist of the Minecraft server.
AI agents use add_to_whitelist to create or update resources in OPanel MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your OPanel MCP environment.
This tool creates or modifies the whitelist—a reversible change to server state. While it affects access permissions, it does not execute arbitrary code, delete data, or move financial assets. The moderate severity reflects that unauthorized whitelist modifications could disrupt server operations or enable/prevent player access, but the effect is containable and reversible through removal from the whitelist.
From the tool's definition Tool name 'add_to_whitelist' and description 'Add a player to the whitelist' indicate creation/modification of server access control data.
Attacks that exploit this kind of access
Add a player to the whitelist of the Minecraft server. It is categorised as a Write tool in the OPanel MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the OPanel MCP server in PolicyLayer and add a rule for add_to_whitelist: 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 OPanel MCP. Nothing to install.
add_to_whitelist 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 add_to_whitelist 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 add_to_whitelist. 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.
add_to_whitelist is provided by the OPanel MCP server (opanel-mc/opanel-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 →