jadx_decompile_apk
High-level JADX APK decompile: decompile the whole APK to a stable output directory and return sourcesDir for jadx_search_code.
This record as markdown: /tools/io-github-vmoranv-jshookmcp/jadx-decompile-apk.md
What jadx_decompile_apk does on Jshookmcp
AI agents call jadx_decompile_apk to permanently remove resources in Jshookmcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why jadx_decompile_apk is rated Critical
An AI agent that decides to call jadx_decompile_apk doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Jshookmcp is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs jadx_decompile_apk safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Jshookmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For jadx_decompile_apk, this is the rule to start with:
jadx_decompile_apk is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Jshookmcp, apply this rule, and every jadx_decompile_apk call is checked against it from then on.
Questions about jadx_decompile_apk
High-level JADX APK decompile: decompile the whole APK to a stable output directory and return sourcesDir for jadx_search_code. It is categorised as a Destructive tool in the Jshookmcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Jshook MCP server in PolicyLayer and add a rule for jadx_decompile_apk: 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 Jshookmcp. Nothing to install.
jadx_decompile_apk is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the jadx_decompile_apk 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 jadx_decompile_apk. 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.
jadx_decompile_apk is provided by the Jshook MCP server (@jshookmcp/jshook). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Jshook, and thousands of servers like it.
Across the catalogue