rename_function · Binary Ninja Cline MCP Server MCP

WHAT IT DOES

What rename_function does on Binary Ninja Cline MCP Server

AI agents use rename_function to create or update resources in Binary Ninja Cline MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Binary Ninja Cline MCP Server environment.

WHY IT NEEDS A POLICY

Why rename_function needs a policy

The tool modifies function names in a binary analysis session, which is a reversible change to metadata (renaming can be undone). It does not delete data (Destructive), execute arbitrary code (Execute), involve financial transactions (Financial), or merely read data (Read). It is a Write operation that changes state within the analysis environment.

From the tool's definition Tool description states 'Rename a function by its current name to a new user-defined name.' This modifies binary analysis metadata within Binary Ninja.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rename_function Rate-limited

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": {
    "rename_function": {
      "limits": [
        {
          "counter": "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 Binary Ninja Cline MCP Server, so you can run agents against it safely.

FAQ

Questions about rename_function

What does the rename_function tool do? +

Rename a function by its current name to a new user-defined name. It is categorised as a Write tool in the Binary Ninja Cline MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on rename_function? +

Register the Binary Ninja Cline MCP Server MCP server in PolicyLayer and add a rule for 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 Binary Ninja Cline MCP Server. Nothing to install.

What risk level is rename_function? +

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

Can I rate-limit rename_function? +

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

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

rename_function is provided by the Binary Ninja Cline MCP Server MCP server (opensensor/bn_cline_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.