AI agents call debug_get_stack_frames 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 retrieves stack frame information during debugging sessions, which is a read-only operation that queries the state of a running process. It has no side effects, does not execute code, does not modify data, and does not delete or move resources. The context of JADX (a decompiler) for reverse engineering Android apps confirms this is inspection/analysis functionality.
From the tool's definition Tool name 'debug_get_stack_frames' and description 'Get current stack frames (call stack)' indicate retrieval of debugging information without modification or execution of code.
Documented attack patterns abuse exactly the kind of access debug_get_stack_frames 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 debug_get_stack_frames:
{
"version": "1",
"default": "deny",
"tools": {
"debug_get_stack_frames": {}
}
}debug_get_stack_frames 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 current stack frames (call stack). 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 debug_get_stack_frames: 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.
debug_get_stack_frames 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 debug_get_stack_frames 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 debug_get_stack_frames. 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.
debug_get_stack_frames 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.