Critical Risk →

digBlock

Dig a block at the specified coordinates

How to control digBlock ↓

What digBlock does on MCP Minecraft Remote

AI agents call digBlock to permanently remove resources in MCP Minecraft Remote — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why digBlock needs a policy

Digging a block in Minecraft removes it from the world, which is an irreversible destructive action (the block and any associated data/placement context is lost). While items may drop, the original placed block state cannot be trivially restored, especially for placed/built structures. This falls under Destructive category.

From the tool's definition Dig a block at the specified coordinates

Documented attack patterns abuse exactly the kind of access digBlock gives an agent:

How to control digBlock

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 digBlock:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "digBlock"
  ]
}

digBlock disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register MCP Minecraft Remote — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about digBlock

What does the digBlock tool do? +

Dig a block at the specified coordinates. It is categorised as a Destructive tool in the MCP Minecraft Remote MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on digBlock? +

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

What risk level is digBlock? +

digBlock is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit digBlock? +

Yes. Add a rate_limit block to the digBlock 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 digBlock completely? +

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

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

Enforce policy on every MCP Minecraft Remote tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.