rename_function · Ghidra MCP: Risk & Policy

WHAT IT DOES

What rename_function does on GhidraMCP

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

WHY IT NEEDS A POLICY

Why rename_function needs a policy

Renaming a function is a reversible modification operation that changes metadata within a Ghidra project. It does not delete or irreversibly destroy data (thus not Destructive), does not execute external code or operations (thus not Execute), and does not move money (thus not Financial). However, this is a Write operation because it persists changes to the binary analysis project.

From the tool's definition Tool description states it "Rename a function by its current name to a new user-defined name" — this modifies existing data (function metadata) in the analyzed binary project.

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 GhidraMCP, 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 GhidraMCP 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 Ghidra 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 GhidraMCP. 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 Ghidra MCP server (pr0cf5/ghidramcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.