Radare2_rename_function · Reversecore

WHAT IT DOES

What Radare2_rename_function does on Reversecore_MCP

AI agents use Radare2_rename_function to create or update resources in Reversecore_MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Reversecore_MCP environment.

WHY IT NEEDS A POLICY

Why Radare2_rename_function needs a policy

Renaming a function in a binary analysis context modifies the internal structure and symbol table of the analyzed binary. This is a reversible write operation that changes how the binary is interpreted and documented, but does not delete data or execute external code.

From the tool's definition Tool name indicates 'rename' action; description states 'Rename the function at the specified address.' This modifies metadata/symbols associated with a binary.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

Radare2_rename_function Rate-limited

Radare2_rename_function stays usable, but capped — an agent stuck in a loop can't make hundreds of changes 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_rename_function": {
      "limits": [
        {
          "counter": "radare2_rename_function_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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_rename_function

What does the Radare2_rename_function tool do? +

Rename the function at the specified address. It is categorised as a Write tool in the Reversecore_MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on Radare2_rename_function? +

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

Radare2_rename_function is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit Radare2_rename_function? +

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

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

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