Analyze the structure of a decoded APK project and provide comprehensive metadata. Args: project_dir: Path to the APKTool project directory Returns: Dictionary with detailed project analysis
AI agents call analyze_project_structure to retrieve information from Apktool MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only operation that queries and retrieves information about an existing project directory without making changes. It fits the Read category pattern of retrieval or analysis with no side effects. Severity is low because reverse engineering analysis itself poses minimal direct risk compared to execution or data modification tools on the same server (decode_apk, build_apk, clean_project).
From the tool's definition Tool analyzes and returns metadata about a decoded APK project structure. The description indicates it 'provide[s] comprehensive metadata' with no mention of modifications, deletion, or code execution.
Documented attack patterns abuse exactly the kind of access analyze_project_structure gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Apktool MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for analyze_project_structure:
{
"version": "1",
"default": "deny",
"tools": {
"analyze_project_structure": {}
}
}analyze_project_structure 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.
Analyze the structure of a decoded APK project and provide comprehensive metadata. Args: project_dir: Path to the APKTool project directory Returns: Dictionary with detailed project analysis. It is categorised as a Read tool in the Apktool MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Apktool MCP Server MCP server in PolicyLayer and add a rule for analyze_project_structure: 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 Apktool MCP Server. Nothing to install.
analyze_project_structure 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 analyze_project_structure 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 analyze_project_structure. 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.
analyze_project_structure is provided by the Apktool MCP Server MCP server (zinja-coder/apktool-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 16 Apktool MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
16 Apktool MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.