Analyze a third-party mod JAR file to extract metadata, dependencies, entry points, mixins, and class information. Supports Fabric, Quilt, Forge, and NeoForge mods. Returns comprehensive mod analysis including: mod ID, version, Minecraft compatibility, dependencies, entry points, mixin configurat...
AI agents call analyze_mod_jar 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 performs static analysis and information retrieval from JAR files without modifying, executing, or destructively altering any data. It examines the structure and contents of existing mod files to provide metadata and class information to the user. While the JAR file originates from a third-party source, the tool itself only reads and reports on its properties.
From the tool's definition Tool extracts and analyzes metadata, dependencies, entry points, mixins, and class information from mod JAR files.
Documented attack patterns abuse exactly the kind of access analyze_mod_jar 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 analyze_mod_jar:
{
"version": "1",
"default": "deny",
"tools": {
"analyze_mod_jar": {}
}
}analyze_mod_jar 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.
Analyze a third-party mod JAR file to extract metadata, dependencies, entry points, mixins, and class information. Supports Fabric, Quilt, Forge, and NeoForge mods. Returns comprehensive mod analysis including: mod ID, version, Minecraft compatibility, dependencies, entry points, mixin configurations, and class statistics. Supports both WSL (/mnt/c/...) and Windows (C:\\...) paths. 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 analyze_mod_jar: 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.
analyze_mod_jar 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 analyze_mod_jar 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 analyze_mod_jar. 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.
analyze_mod_jar 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.