Fetch main application classes' names from Manifest package.
AI agents call get_main_application_classes_names 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 performs a straightforward data retrieval operation—fetching application class names from the package manifest. It has no side effects, makes no modifications, executes no code, and poses minimal security risk. The information retrieved (class names) is metadata that would be accessible through normal APK inspection. Classification as Read is appropriate.
From the tool's definition Tool name contains 'get' and description uses 'Fetch', both indicative of read-only retrieval. The tool extracts class names from the Android Manifest file without modifying data.
Documented attack patterns abuse exactly the kind of access get_main_application_classes_names 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 get_main_application_classes_names:
{
"version": "1",
"default": "deny",
"tools": {
"get_main_application_classes_names": {}
}
}get_main_application_classes_names 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 main application classes' names from Manifest package. 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 get_main_application_classes_names: 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.
get_main_application_classes_names 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 get_main_application_classes_names 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 get_main_application_classes_names. 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.
get_main_application_classes_names 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.