Decompile an APK/XAPK/JAR/AAR file using the selected engine.
AI agents invoke decompile to trigger actions in Android Reverse Engineering. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes a decompilation process on binary files, triggering an external operation (decompilation engine) that processes arbitrary files. It runs code/tooling on provided input, making it an Execute category. High severity because it runs external tools on potentially untrusted binary files, which could be exploited via malicious APKs or path traversal.
From the tool's definition Decompile an APK/XAPK/JAR/AAR file using the selected engine
Documented attack patterns abuse exactly the kind of access decompile gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Android Reverse Engineering, and nothing reaches the server without passing your rules. This is the rule we recommend for decompile:
{
"version": "1",
"default": "deny",
"tools": {
"decompile": {
"limits": [
{
"counter": "decompile_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}decompile stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Decompile an APK/XAPK/JAR/AAR file using the selected engine. It is categorised as a Execute tool in the Android Reverse Engineering MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Android Reverse Engineering MCP server in PolicyLayer and add a rule for decompile: 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 Android Reverse Engineering. Nothing to install.
decompile is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the decompile 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 decompile. 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.
decompile is provided by the Android Reverse Engineering MCP server (vichhka-git/android-reverse-engineering-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Android Reverse Engineering, 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.
6 Android Reverse Engineering tools catalogued and risk-classified — across an index of 43,000+ MCP servers.