Radare2_decompile_function · Reversecore

WHAT IT DOES

What Radare2_decompile_function does on Reversecore_MCP

AI agents invoke Radare2_decompile_function 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_decompile_function needs a policy

Radare2's decompile function operation runs analysis/decompilation commands against a binary target. This falls under Execute as it triggers external tool operations (Radare2) to process and decompile binary code. The description is empty, which lowers confidence, but the name and server context strongly suggest this executes Radare2 decompilation commands.

From the tool's definition Tool name 'Radare2_decompile_function' on a reverse engineering MCP server that uses Radare2, a binary analysis framework capable of executing analysis operations on binaries.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

Radare2_decompile_function Rate-limited

Radare2_decompile_function 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_decompile_function": {
      "limits": [
        {
          "counter": "radare2_decompile_function_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_decompile_function

What does the Radare2_decompile_function tool do? +

Radare2_decompile_function. 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_decompile_function? +

Register the Reversecore_ MCP server in PolicyLayer and add a rule for Radare2_decompile_function: 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_decompile_function? +

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

Can I rate-limit Radare2_decompile_function? +

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

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

Radare2_decompile_function 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.