AI agents call check_cfr_status to retrieve information from Java Decompiler 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 or queries the current state of the CFR decompiler (e.g., availability, version, configuration) without modifying any data, executing arbitrary code, or affecting system state. It is purely informational, making it a Read category risk with low severity.
From the tool's definition Tool name 'check_cfr_status' and description 'Check CFR decompiler status' indicate a status query operation. The verb 'check' and 'status' are inspection/query actions with no side effects.
Documented attack patterns abuse exactly the kind of access check_cfr_status 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 check_cfr_status:
{
"version": "1",
"default": "deny",
"tools": {
"check_cfr_status": {}
}
}check_cfr_status 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.
检查 CFR 反编译器状态. It is categorised as a Read tool in the Java Decompiler MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Java Decompiler MCP Server MCP server in PolicyLayer and add a rule for check_cfr_status: 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.
check_cfr_status 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 check_cfr_status 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 check_cfr_status. 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.
check_cfr_status 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.