// SCAN REPORT

JADX-MCP-SERVER

32 tools. 6 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 10 Jun 2026

6 can modify or destroy data

26 read-only

32 tools total

Community server · catalogue entry verified 10/06/2026

How to control JADX-MCP-SERVER ↓

TOOL MAP

Read (26) Write / Execute (5) Destructive / Financial (1)

MOST DANGEROUS TOOLS

Critical Risk

Destructive · Medium clear_cache Clearing a cache and resetting counters is an irreversible operation; once cleared, the cached decompilation data and counter state cannot be recovered without re-decompiling. Write · Medium rename_class Renaming a class is a reversible modification operation that changes code structure but does not delete data or execute external operations. Write · Medium rename_field The tool modifies field metadata (the name) in decompiled code analysis state, which is reversible and does not delete data or execute arbitrary logic. Write · High rename_method Renaming a method is a Write operation because it modifies the decompiled code analysis state in a way that can be undone (e.g., by clearing cache or reverting changes).

6 of JADX-MCP-SERVER's 32 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

HOW TO CONTROL JADX-MCP-SERVER

PolicyLayer is an MCP gateway — it sits between your AI agents and JADX-MCP-SERVER, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "clear_cache": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "rename_class": {
    "limits": [
      {
        "counter": "rename_class_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "debug_get_stack_frames": {
    "limits": [
      {
        "counter": "debug_get_stack_frames_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register JADX-MCP-SERVER — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON JADX-MCP-SERVER →

Free to start. No card required.

ALL 32 JADX-MCP-SERVER TOOLS

DESTRUCTIVE 1 tools

Destructive clear_cache Clear the decompilation source cache and reset counters. Use when switching APKs or to free memory.

WRITE 5 tools

Write rename_class Renames a specific class. Write rename_field Renames a specific field. Write rename_method Renames a specific method. Write rename_package Renames a package and all its classes. Write rename_variable Renames a specific variable in a method.

READ 26 tools

Read debug_get_stack_frames Get current stack frames (call stack). Read debug_get_threads Get all threads in the debugged process. Read debug_get_variables Get current variables when process is suspended. Read fetch_current_class Fetch the currently selected class and its code from the JADX-GUI plugin. Read get_all_classes Returns a list of all classes in the project with pagination support. Read get_all_resource_file_names Retrieve all resource files names. Read get_android_manifest Retrieve and return the AndroidManifest.xml content. Read get_cache_stats Get decompilation cache statistics: hits, misses, hit_rate, cached_classes, compressed_mb, compression_ratio. Read get_class_source Fetch the Java source of a specific class. Read get_fields_of_class List all field names in a class. Read get_main_activity_class Fetch the main activity class from AndroidManifest.xml. Read get_main_application_classes_code Fetch main application classes' code with pagination. Read get_main_application_classes_names Fetch main application classes' names from Manifest package. Read get_manifest_component Retrieve specified component data from AndroidManifest.xml, support filter exported components. Support st Read get_method_by_name Fetch the source code of a method from a specific class. Read get_methods_of_class List all method names in a class. Read get_package_tree Get all packages in the APK sorted by class count. Shows total_classes, total_packages, and per-package name, Read get_resource_file Retrieve resource file content. Read get_selected_text Returns the currently selected text in the decompiled code view. Read get_smali_of_class Fetch the smali representation of a class. Read get_strings Retrieve contents of strings.xml files. Read get_xrefs_to_class Find all references to a class. Read get_xrefs_to_field Find all references to a field. Read get_xrefs_to_method Find all references to a method. Read search_classes_by_keyword search_classes_by_keyword Read search_method_by_name Search for a method name across all classes.

RELATED SERVERS

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Can an AI agent delete data through the JADX-MCP-SERVER MCP server? +

Yes. The JADX-MCP-SERVER server exposes 1 destructive tools including clear_cache. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through JADX-MCP-SERVER? +

The JADX-MCP-SERVER server has 5 write tools including rename_class, rename_field, rename_method. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach JADX-MCP-SERVER.

How many tools does the JADX-MCP-SERVER MCP server expose? +

32 tools across 3 categories: Destructive, Read, Write. 26 are read-only. 6 can modify, create, or delete data.

How do I enforce a policy on JADX-MCP-SERVER? +

Register the JADX-MCP-SERVER MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every JADX-MCP-SERVER tool call.

Deterministic rules across all 32 JADX-MCP-SERVER tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON JADX-MCP-SERVER →

Free to start. No card required.

32 JADX-MCP-SERVER tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

JADX-MCP-SERVER

// TOOL MAP

// MOST DANGEROUS TOOLS

// HOW TO CONTROL JADX-MCP-SERVER

// ALL 32 JADX-MCP-SERVER TOOLS

// RELATED SERVERS

// FAQ