AI agents call disassemble_function to retrieve information from GhidraMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs static analysis—disassembly and display of existing binary code—without modifying the target application, executing code, or triggering external operations. It is a read-only information retrieval operation typical of reverse engineering tools. The low severity reflects minimal blast radius: misuse would only expose binary information already present in the analyzed application.
From the tool's definition Tool retrieves assembly code for a function, returning address-instruction-comment tuples. No modification, deletion, or execution is performed. The description explicitly states 'Get', indicating data retrieval with no side effects.
Attacks that exploit this kind of access
Get assembly code (address: instruction; comment) for a function. It is categorised as a Read tool in the GhidraMCP MCP Server, which means it retrieves data without modifying state.
Register the Ghidra MCP server in PolicyLayer and add a rule for disassemble_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.
disassemble_function is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the disassemble_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.
Set action: deny in the PolicyLayer policy for disassemble_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.
disassemble_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →