Dig a block at the specified position
AI agents call dig-block to permanently remove resources in Minecraft MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Digging a block in Minecraft removes it from its position in the world. While the block may drop as an item, the original placement/structure is permanently altered and cannot be automatically undone. This constitutes irreversible destruction of in-game world data, placing it in the Destructive category.
From the tool's definition 'Dig a block at the specified position' — digging removes a block from the world, which is an irreversible destructive action (the block and its placement are destroyed).
Attacks that exploit this kind of access
Dig a block at the specified position. It is categorised as a Destructive tool in the Minecraft MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Minecraft MCP Server MCP server in PolicyLayer and add a rule for dig-block: 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 Minecraft MCP Server. Nothing to install.
dig-block 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 dig-block 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 dig-block. 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.
dig-block is provided by the Minecraft MCP Server MCP server (zeeweebee/mcp-server). 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 →