AI agents invoke closeContainer to trigger actions in MCP Minecraft Remote. 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.
This tool executes an in-game action on a remote Minecraft server, closing a currently open container (chest, furnace, etc.). It causes a side effect in the game world but does not delete data, move money, or create/modify persistent data in a meaningful way. It's an execution of a game interaction command.
From the tool's definition 'Close the currently open container' — triggers an external operation (closing a UI/container) in the Minecraft game environment
Documented attack patterns abuse exactly the kind of access closeContainer gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Minecraft Remote, and nothing reaches the server without passing your rules. This is the rule we recommend for closeContainer:
{
"version": "1",
"default": "deny",
"tools": {
"closeContainer": {
"limits": [
{
"counter": "closecontainer_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}closeContainer 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.
Free to start. No card required.
Close the currently open container. It is categorised as a Execute tool in the MCP Minecraft Remote MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Minecraft Remote MCP server in PolicyLayer and add a rule for closeContainer: 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 MCP Minecraft Remote. Nothing to install.
closeContainer 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 closeContainer 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 closeContainer. 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.
closeContainer is provided by the MCP Minecraft Remote MCP server (nacal/mcp-minecraft-remote). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Minecraft Remote, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
27 MCP Minecraft Remote tools catalogued and risk-classified — across an index of 43,000+ MCP servers.