Modify smali file content with validation and backup support. Args: project_dir: Path to the APKTool project directory class_name: Full class name (e.g., com.example.MyClass) new_content: New content for the smali file create_backup: Whether to create a backup of the original file Returns: Dictio...
AI agents use modify_smali_file to create or update resources in Apktool MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Apktool MCP Server environment.
This is a Write operation because it creates or modifies data reversibly (the backup support enables undo). However, severity is high rather than medium because modifying smali bytecode in Android applications could inject malicious code, alter application behavior, bypass security checks, or compromise app integrity.
From the tool's definition Tool performs 'Modify smali file content' - directly alters bytecode in Android applications with 'new_content' parameter and optional backup support. Smali files are the dissembled Java bytecode representation that can be recompiled into APK binaries.
Documented attack patterns abuse exactly the kind of access modify_smali_file 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 modify_smali_file:
{
"version": "1",
"default": "deny",
"tools": {
"modify_smali_file": {
"limits": [
{
"counter": "modify_smali_file_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}modify_smali_file stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Modify smali file content with validation and backup support. Args: project_dir: Path to the APKTool project directory class_name: Full class name (e.g., com.example.MyClass) new_content: New content for the smali file create_backup: Whether to create a backup of the original file Returns: Dictionary with operation results and metadata. It is categorised as a Write tool in the Apktool MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Apktool MCP Server MCP server in PolicyLayer and add a rule for modify_smali_file: 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.
modify_smali_file is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the modify_smali_file 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 modify_smali_file. 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.
modify_smali_file 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.