Get Minecraft registry data (blocks, items, entities, etc.). This runs the data generator if not cached.
AI agents call get_registry_data to retrieve information from Minecraft Dev MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries Minecraft registry data. Although it 'runs the data generator if not cached,' this is a read-like operation that generates or loads existing data structures without creating, modifying, or deleting persistent game data. The output is informational registry metadata. No side effects on game state or persistent modifications occur. This is a classic Read category use case.
From the tool's definition Tool description states 'Get Minecraft registry data' and 'runs the data generator if not cached' — these are retrieval/query operations with no modification of data. The tool reads existing registry information (blocks, items, entities, etc.) from Minecraft.
Documented attack patterns abuse exactly the kind of access get_registry_data gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Minecraft Dev MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_registry_data:
{
"version": "1",
"default": "deny",
"tools": {
"get_registry_data": {}
}
} get_registry_data is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get Minecraft registry data (blocks, items, entities, etc.). This runs the data generator if not cached. It is categorised as a Read tool in the Minecraft Dev MCP MCP Server, which means it retrieves data without modifying state.
Register the Minecraft Dev MCP server in PolicyLayer and add a rule for get_registry_data: 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 Dev MCP. Nothing to install.
get_registry_data is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_registry_data 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 get_registry_data. 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.
get_registry_data is provided by the Minecraft Dev MCP server (mcdxai/minecraft-dev-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Minecraft Dev MCP, 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.
20 Minecraft Dev MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.