AI agents call get_current_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 retrieves information about which function is currently selected in Ghidra's UI—a read-only query operation with no side effects. It does not execute code, modify data, or trigger external operations. While GhidraMCP as a whole enables reverse engineering, this specific tool is purely informational, similar to 'get_current_address' and other sibling list/get tools on the server.
From the tool's definition Tool name 'get_current_function' and description 'Get the function currently selected by the user' indicate retrieval of metadata about the current selection state without modification or execution.
Attacks that exploit this kind of access
Get the function currently selected by the user. 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 get_current_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.
get_current_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 get_current_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 get_current_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.
get_current_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 →