Fetch the currently selected class and its code from the JADX-GUI plugin.
AI agents call fetch_current_class to retrieve information from JADX-MCP-SERVER without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves decompiled source code and metadata from a static analysis tool (JADX). It has no side effects—it only queries and returns existing data without modifying the analyzed application, the JADX state, or any external system. The highest risk would be information disclosure if sensitive code is exposed, but that is inherent to the analysis activity itself, not this tool's mechanism.
From the tool's definition Tool name is 'fetch_current_class' and description states it 'Fetch[es] the currently selected class and its code from the JADX-GUI plugin.' The verb 'fetch' combined with 'retrieves' class code with no mention of modification, deletion, or execution.
Documented attack patterns abuse exactly the kind of access fetch_current_class gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and JADX-MCP-SERVER, and nothing reaches the server without passing your rules. This is the rule we recommend for fetch_current_class:
{
"version": "1",
"default": "deny",
"tools": {
"fetch_current_class": {}
}
}fetch_current_class 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.
Fetch the currently selected class and its code from the JADX-GUI plugin. It is categorised as a Read tool in the JADX-MCP-SERVER MCP Server, which means it retrieves data without modifying state.
Register the JADX-MCP-SERVER MCP server in PolicyLayer and add a rule for fetch_current_class: 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 JADX-MCP-SERVER. Nothing to install.
fetch_current_class 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 fetch_current_class 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 fetch_current_class. 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.
fetch_current_class is provided by the JADX-MCP-SERVER MCP server (zinja-coder/jadx-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 32 JADX-MCP-SERVER tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
32 JADX-MCP-SERVER tools catalogued and risk-classified — across an index of 42,500+ MCP servers.