AI agents call decompile_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 reads and transforms binary data into decompiled C code. It only retrieves/queries information from the binary being analyzed and returns it — no side effects, no writes, no execution of the decompiled code.
From the tool's definition Decompile a specific function by name and return the decompiled C code
Attacks that exploit this kind of access
Decompile a specific function by name and return the decompiled C code. 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 decompile_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.
decompile_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 decompile_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 decompile_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.
decompile_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 →