Remove a player from the server whitelist
AI agents call mc_whitelist_remove to permanently remove resources in Mc Rcon — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a player from the whitelist is a destructive action that immediately revokes their ability to join the server. While the player data itself isn't deleted, the access revocation is an irreversible side effect (the player is locked out until manually re-added). This is more severe than a simple write/update and qualifies as destructive. Misuse by an AI agent could deny access to legitimate players.
From the tool's definition 'Remove a player from the server whitelist' — removing from whitelist revokes access and is not easily reversible without re-adding the player manually
Attacks that exploit this kind of access
Remove a player from the server whitelist. It is categorised as a Destructive tool in the Mc Rcon MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mc Rcon MCP server in PolicyLayer and add a rule for mc_whitelist_remove: 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 Mc Rcon. Nothing to install.
mc_whitelist_remove is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the mc_whitelist_remove 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 mc_whitelist_remove. 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.
mc_whitelist_remove is provided by the Mc Rcon MCP server (pedxyuyuko/mc-rcon-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 →