set_decompiler_comment · Ghidra MCP: Risk & Policy

WHAT IT DOES

What set_decompiler_comment does on GhidraMCP

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

This tool creates or modifies decompiler comments associated with code addresses. While comments are reversible metadata rather than structural code changes, they do alter the analysis state persistently. The tool falls under Write rather than Read (it modifies, not just retrieves) and does not rise to Execute (no command execution or external operations triggered).

From the tool's definition Tool name 'set_decompiler_comment' and description 'Set a comment for a given address in the function pseudocode' indicate creation/modification of metadata (comments) within the Ghidra analysis database.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_decompiler_comment Rate-limited

set_decompiler_comment 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": {
    "set_decompiler_comment": {
      "limits": [
        {
          "counter": "set_decompiler_comment_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 set_decompiler_comment

What does the set_decompiler_comment tool do? +

Set a comment for a given address in the function pseudocode. 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 set_decompiler_comment? +

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

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

Can I rate-limit set_decompiler_comment? +

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

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

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