kick_player · OPanel MCP: Risk & Policy

WHAT IT DOES

What kick_player does on OPanel MCP

AI agents invoke kick_player to trigger actions in OPanel 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.

WHY IT NEEDS A POLICY

Why kick_player needs a policy

Kicking a player is an action that triggers an external operation (forcibly disconnecting a player from the server). It is not purely destructive (the player can rejoin), nor does it modify stored data. It executes an administrative command with real but reversible effects, fitting the Execute category. Misuse could disrupt legitimate players but has limited blast radius.

From the tool's definition Kick a player from the Minecraft server

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

kick_player Rate-limited

kick_player stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "kick_player": {
      "limits": [
        {
          "counter": "kick_player_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches OPanel MCP, so you can run agents against it safely.

FAQ

Questions about kick_player

What does the kick_player tool do? +

Kick a player from the Minecraft server. It is categorised as a Execute tool in the OPanel MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on kick_player? +

Register the OPanel MCP server in PolicyLayer and add a rule for kick_player: 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.

What risk level is kick_player? +

kick_player is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit kick_player? +

Yes. Add a rate_limit block to the kick_player 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.

How do I block kick_player completely? +

Set action: deny in the PolicyLayer policy for kick_player. 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.

What MCP server provides kick_player? +

kick_player 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.