rename_data · Ghidra MCP: Risk & Policy

WHAT IT DOES

What rename_data does on GhidraMCP

AI agents use rename_data 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_data needs a policy

This tool modifies Ghidra project metadata (data labels) reversibly without deleting underlying data or executing external operations. Renaming is a write operation that can be undone or corrected. While it could mislead analysis if misused, it does not irreversibly destroy data (Destructive), execute arbitrary code (Execute), or move money (Financial).

From the tool's definition Tool name 'rename_data' and description 'Rename a data label at the specified address' indicate modification of existing data labels within Ghidra's analysis database.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rename_data Rate-limited

rename_data 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_data": {
      "limits": [
        {
          "counter": "rename_data_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_data

What does the rename_data tool do? +

Rename a data label at the specified 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_data? +

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

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

Can I rate-limit rename_data? +

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

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

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