rename_function_by_address · Ghidra MCP: Risk & Policy

WHAT IT DOES

What rename_function_by_address does on GhidraMCP

AI agents use rename_function_by_address 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_by_address needs a policy

Renaming a function changes project state and metadata but does not delete or irreversibly destroy data. The operation is reversible (can be renamed again). Severity is medium because misuse could corrupt analysis work or introduce misleading function names that degrade reverse engineering quality, but the harm is limited to the analyst's own Ghidra project and can be undone.

From the tool's definition Tool description states 'Rename a function by its address.' The action of renaming modifies metadata within a Ghidra project reversibly—the old name can be restored.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rename_function_by_address Rate-limited

rename_function_by_address 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_by_address": {
      "limits": [
        {
          "counter": "rename_function_by_address_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_by_address

What does the rename_function_by_address tool do? +

Rename a function by its address. 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_by_address? +

Register the Ghidra MCP server in PolicyLayer and add a rule for rename_function_by_address: 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_by_address? +

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

Can I rate-limit rename_function_by_address? +

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

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

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