AI agents call decompile_directory to permanently remove resources in Java Decompiler MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
An AI agent that decides to call decompile_directory doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Java Decompiler MCP Server is gone — there is no undo for destructive operations.
Documented attack patterns abuse exactly the kind of access decompile_directory gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Java Decompiler MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for decompile_directory:
{
"version": "1",
"default": "deny",
"hide": [
"decompile_directory"
]
}decompile_directory 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.
decompile_directory. It is categorised as a Destructive tool in the Java Decompiler MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Java Decompiler MCP Server MCP server in PolicyLayer and add a rule for decompile_directory: 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 Java Decompiler MCP Server. Nothing to install.
decompile_directory 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 decompile_directory 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 decompile_directory. 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.
decompile_directory is provided by the Java Decompiler MCP Server MCP server (ruoji6/java-decompile-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 6 Java Decompiler MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
6 Java Decompiler MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.