Open a container (chest, furnace, etc.) at specific coordinates
AI agents invoke openContainer 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.
Opening a container triggers an external interaction in the Minecraft game world — it initiates an in-game action (opening a chest, furnace, or other container) at specified coordinates. This is an execution of a game-world operation rather than a simple read, as it changes the game state (the container becomes open/active) and could expose or enable access to inventory contents for further manipulation.
From the tool's definition Open a container (chest, furnace, etc.) at specific coordinates
Documented attack patterns abuse exactly the kind of access openContainer 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 openContainer:
{
"version": "1",
"default": "deny",
"tools": {
"openContainer": {
"limits": [
{
"counter": "opencontainer_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}openContainer 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.
Open a container (chest, furnace, etc.) at specific coordinates. 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 openContainer: 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.
openContainer 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 openContainer 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 openContainer. 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.
openContainer 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.