Clean a project directory to prepare for rebuilding with enhanced backup support. Args: project_dir: Path to the APKTool project directory backup: Whether to create a backup of build directories before cleaning Returns: Dictionary with operation results and cleanup details
AI agents call clean_project to permanently remove resources in Apktool MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Cleaning a project directory removes build artifacts and files irreversibly. While a backup option exists, the primary action is deletion/removal of directory contents. If backup=False, data is permanently lost.
From the tool's definition Clean a project directory to prepare for rebuilding with enhanced backup support
Documented attack patterns abuse exactly the kind of access clean_project 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 clean_project:
{
"version": "1",
"default": "deny",
"hide": [
"clean_project"
]
}clean_project disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Clean a project directory to prepare for rebuilding with enhanced backup support. Args: project_dir: Path to the APKTool project directory backup: Whether to create a backup of build directories before cleaning Returns: Dictionary with operation results and cleanup details. It is categorised as a Destructive tool in the Apktool MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Apktool MCP Server MCP server in PolicyLayer and add a rule for clean_project: 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.
clean_project is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the clean_project 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 clean_project. 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.
clean_project 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.