Get detailed information about a specific Minecraft class including all its methods and fields with their parameter names and Javadocs.
AI agents call get_class_details to retrieve information from Mcmodding without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves static documentation and metadata about Minecraft classes. It performs a query operation over the modding documentation index with no capability to modify, delete, execute code, or cause irreversible changes. The worst-case misuse would be information gathering, which has minimal blast radius. Classified as Read with low severity.
From the tool's definition Tool name 'get_class_details' and description 'Get detailed information about a specific Minecraft class including all its methods and fields' indicates retrieval of documentation and metadata with no side effects.
Documented attack patterns abuse exactly the kind of access get_class_details gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcmodding, and nothing reaches the server without passing your rules. This is the rule we recommend for get_class_details:
{
"version": "1",
"default": "deny",
"tools": {
"get_class_details": {}
}
}get_class_details 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 detailed information about a specific Minecraft class including all its methods and fields with their parameter names and Javadocs. It is categorised as a Read tool in the Mcmodding MCP Server, which means it retrieves data without modifying state.
Register the Mcmodding MCP server in PolicyLayer and add a rule for get_class_details: 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 Mcmodding. Nothing to install.
get_class_details 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_class_details 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_class_details. 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_class_details is provided by the Mcmodding MCP server (ogmatrix/mcmodding-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 15 Mcmodding tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
15 Mcmodding tools catalogued and risk-classified — across an index of 42,500+ MCP servers.