Low Risk

lookup_obfuscated

Look up the deobfuscated name for an obfuscated Minecraft class, method, or field name. Useful when encountering obfuscated names in crash logs or decompiled code.

How to control lookup_obfuscated ↓

AI agents call lookup_obfuscated 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.

Low Risk

This tool performs a simple dictionary lookup to resolve Minecraft's obfuscated identifiers to their human-readable deobfuscated names. It is purely informational, analogous to a search or fetch operation. There are no side effects, no code execution, no data modification, and no destructive actions.

From the tool's definition Tool description states it 'Look[s] up the deobfuscated name' — a lookup/retrieval operation with no side effects. The verb 'look up' indicates a query operation that returns information without modifying, creating, or deleting data.

Documented attack patterns abuse exactly the kind of access lookup_obfuscated 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 lookup_obfuscated:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "lookup_obfuscated": {}
  }
}

lookup_obfuscated is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Mcmodding — 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.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the lookup_obfuscated tool do? +

Look up the deobfuscated name for an obfuscated Minecraft class, method, or field name. Useful when encountering obfuscated names in crash logs or decompiled code. It is categorised as a Read tool in the Mcmodding MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on lookup_obfuscated? +

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

What risk level is lookup_obfuscated? +

lookup_obfuscated is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit lookup_obfuscated? +

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

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

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

Enforce policy on every Mcmodding tool call.

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.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.