Get decompilation cache statistics: hits, misses, hit_rate, cached_classes, compressed_mb, compression_ratio.
AI agents call get_cache_stats to retrieve information from JADX-MCP-SERVER without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns cache performance statistics without side effects. It is a pure read operation that retrieves existing data about the decompilation cache state. No data is modified, no code is executed, and no resources are consumed beyond the query itself. The blast radius of misuse is negligible—returning incorrect cache stats cannot harm the system or data.
From the tool's definition Tool name 'get_cache_stats' and description 'Get decompilation cache statistics' indicate retrieval of metrics only (hits, misses, hit_rate, cached_classes, compressed_mb, compression_ratio). No modification, deletion, or execution capability.
Documented attack patterns abuse exactly the kind of access get_cache_stats 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 get_cache_stats:
{
"version": "1",
"default": "deny",
"tools": {
"get_cache_stats": {}
}
}get_cache_stats 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 decompilation cache statistics: hits, misses, hit_rate, cached_classes, compressed_mb, compression_ratio. It is categorised as a Read tool in the JADX-MCP-SERVER MCP Server, which means it retrieves data without modifying state.
Register the JADX-MCP-SERVER MCP server in PolicyLayer and add a rule for get_cache_stats: 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.
get_cache_stats 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_cache_stats 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_cache_stats. 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_cache_stats 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.