Radare2_use_decompiler · Reversecore

WHAT IT DOES

What Radare2_use_decompiler does on Reversecore_MCP

AI agents invoke Radare2_use_decompiler to trigger actions in Reversecore_MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why Radare2_use_decompiler needs a policy

Selecting and activating a decompiler backend constitutes an external operation that runs a specific analysis engine. While the primary effect is configuration/selection, it directly triggers or switches an active execution backend in the reverse engineering pipeline. No data is irreversibly destroyed, no money is moved, but it does invoke an external process/tool, placing it in Execute.

From the tool's definition 'Select which decompiler backend to use' — triggers execution of a decompiler tool/backend in the Radare2 binary analysis environment

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

Radare2_use_decompiler Rate-limited

Radare2_use_decompiler stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "Radare2_use_decompiler": {
      "limits": [
        {
          "counter": "radare2_use_decompiler_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Reversecore_MCP, so you can run agents against it safely.

FAQ

Questions about Radare2_use_decompiler

What does the Radare2_use_decompiler tool do? +

Select which decompiler backend to use. It is categorised as a Execute tool in the Reversecore_MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on Radare2_use_decompiler? +

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

What risk level is Radare2_use_decompiler? +

Radare2_use_decompiler is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit Radare2_use_decompiler? +

Yes. Add a rate_limit block to the Radare2_use_decompiler 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 Radare2_use_decompiler completely? +

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

Radare2_use_decompiler is provided by the Reversecore_ MCP server (sjkim1127/reversecore_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.