Critical Risk →

apk_decompile

APK反编译分析

How to control apk_decompile ↓

AI agents call apk_decompile to permanently remove resources in Kali Security MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

An AI agent that decides to call apk_decompile doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Kali Security MCP is gone — there is no undo for destructive operations.

Documented attack patterns abuse exactly the kind of access apk_decompile gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Kali Security MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for apk_decompile:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "apk_decompile"
  ]
}

apk_decompile disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Kali Security MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the apk_decompile tool do? +

APK反编译分析. It is categorised as a Destructive tool in the Kali Security MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on apk_decompile? +

Register the Kali Security MCP server in PolicyLayer and add a rule for apk_decompile: 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 Kali Security MCP. Nothing to install.

What risk level is apk_decompile? +

apk_decompile is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit apk_decompile? +

Yes. Add a rate_limit block to the apk_decompile 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.

How do I block apk_decompile completely? +

Set action: deny in the PolicyLayer policy for apk_decompile. 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.

What MCP server provides apk_decompile? +

apk_decompile is provided by the Kali Security MCP server (seac-25/kali-security-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Kali Security MCP tool call.

Deterministic rules across all 249 Kali Security MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

249 Kali Security MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.