AI agents use depositItem to create or update resources in MCP Minecraft Remote — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Minecraft Remote environment.
Depositing items into a container modifies game state (inventory and container contents) but is generally reversible since items can be retrieved. This is a Write operation with medium severity since an AI agent misusing this could move valuable or critical items into unintended containers, but the action is not irreversible.
From the tool's definition 'Put items into an open container' — moves items from inventory into a container, a reversible write operation
Documented attack patterns abuse exactly the kind of access depositItem 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 depositItem:
{
"version": "1",
"default": "deny",
"tools": {
"depositItem": {
"limits": [
{
"counter": "deposititem_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} depositItem stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Put items into an open container. It is categorised as a Write tool in the MCP Minecraft Remote MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Minecraft Remote MCP server in PolicyLayer and add a rule for depositItem: 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.
depositItem 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 depositItem 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 depositItem. 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.
depositItem 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.