// MCP TOOL REFERENCE

ANDROID REVERSE ENGINEERING TOOLS

6 tools from the Android Reverse Engineering MCP Server, categorised by risk level.

View the Android Reverse Engineering policy →
// ALL 6 ANDROID REVERSE ENGINEERING TOOLS
READ 3 tools
Read check_dependencies Check system dependencies required for decompilation. Read find_api_calls Search decompiled sources for API calls and endpoints. Read list_docs List available documentation keys.
EXECUTE 3 tools
Execute decompile Decompile an APK/XAPK/JAR/AAR file using the selected engine. Execute workflow Run dependency check, decompile, and API scan in one step. Execute install_dependency Install a named dependency using the bundled installer script.

Route Android Reverse Engineering through PolicyLayer and every one of its 6 tools is checked against your policy before it runs.

CHECK YOUR STACK →

See every tool, the dangerous ones, and the token cost across your stack.

// FAQ
How many tools does the Android Reverse Engineering MCP server have? +

The Android Reverse Engineering MCP server exposes 6 tools across 2 categories: Read, Execute.

How do I enforce policies on Android Reverse Engineering tools? +

Route the Android Reverse Engineering server through the PolicyLayer gateway. Define allow, deny, or approval rules per tool in the dashboard; they are enforced on every call before it reaches the server.

What risk categories do Android Reverse Engineering tools fall into? +

Android Reverse Engineering tools are categorised as Read (3), Execute (3). Each category has a recommended default policy.

Enforce policy on every Android Reverse Engineering tool call.

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.

CHECK YOUR STACK →

Free to start. No card required.

43,000+ MCP servers and 220,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.