Fetch the main activity class from AndroidManifest.xml.
AI agents call get_main_activity_class 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 reads metadata from an Android manifest file to identify the main activity entry point. It performs a query operation with no side effects, no code execution, and no data modification. The returned information is static configuration data from the app's manifest. The blast radius of misuse is minimal—an agent cannot cause damage by learning which activity is the entry point.
From the tool's definition Tool name is 'get_main_activity_class' and description states 'Fetch the main activity class from AndroidManifest.xml.' The verb 'Fetch' indicates data retrieval without modification.
Documented attack patterns abuse exactly the kind of access get_main_activity_class 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_activity_class:
{
"version": "1",
"default": "deny",
"tools": {
"get_main_activity_class": {}
}
}get_main_activity_class 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 the main activity class from AndroidManifest.xml. 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_activity_class: 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_activity_class 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_activity_class 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_activity_class. 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_activity_class 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.