Clear the decompilation source cache and reset counters. Use when switching APKs or to free memory.
AI agents call clear_cache to permanently remove resources in JADX-MCP-SERVER — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Clearing a cache and resetting counters is an irreversible operation; once cleared, the cached decompilation data and counter state cannot be recovered without re-decompiling. This fits the Destructive category. Severity is medium because it only affects in-memory/local cache data (no persistent user data or external systems are harmed), but misuse could disrupt an active reverse-engineering session.
From the tool's definition 'Clear the decompilation source cache and reset counters' — explicitly clears cached data and resets state, which is irreversible (cached decompilation results and counters are lost).
Documented attack patterns abuse exactly the kind of access clear_cache 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 clear_cache:
{
"version": "1",
"default": "deny",
"hide": [
"clear_cache"
]
}clear_cache 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.
Clear the decompilation source cache and reset counters. Use when switching APKs or to free memory. It is categorised as a Destructive tool in the JADX-MCP-SERVER MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the JADX-MCP-SERVER MCP server in PolicyLayer and add a rule for clear_cache: 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.
clear_cache 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 clear_cache 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 clear_cache. 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.
clear_cache 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.