Get apktool.yml information from a decoded APK project with validation. Args: project_dir: Path to APKTool project directory Returns: Dictionary with apktool.yml content, metadata, and validation results
AI agents call get_apktool_yml 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 tool reads configuration metadata from an already-decoded APK project directory. It performs no modifications, deletions, code execution, or external operations. The blast radius is minimal—an agent could learn about APK structure but cannot alter or execute anything through this tool alone. Classified as Read.
From the tool's definition Tool retrieves 'apktool.yml information from a decoded APK project' and returns 'Dictionary with apktool.yml content, metadata, and validation results'. The verb 'Get' and return of configuration data indicate pure information retrieval with no side effects.
Documented attack patterns abuse exactly the kind of access get_apktool_yml 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 get_apktool_yml:
{
"version": "1",
"default": "deny",
"tools": {
"get_apktool_yml": {}
}
}get_apktool_yml 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.
Get apktool.yml information from a decoded APK project with validation. Args: project_dir: Path to APKTool project directory Returns: Dictionary with apktool.yml content, metadata, and validation results. 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 get_apktool_yml: 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.
get_apktool_yml 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_apktool_yml 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_apktool_yml. 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_apktool_yml 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.