get_current_address
Get the address currently selected in Ghidra
Part of the Ghidra MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
WHEN AI AGENTS USE THIS TOOL
AI agents call get_current_address to retrieve information from Ghidra without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions — but you may still want rate limits to control API costs.
WHY ENFORCE A POLICY ON GET_CURRENT_ADDRESS
Even though get_current_address only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
RECOMMENDED POLICY
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
get_current_address:
rules:
- action: allowSee the full Ghidra policy for all 27 tools.
DETAILS
MORE GHIDRA TOOLS
list_methods Read list_classes Read list_functions Read list_segments Read list_imports Read list_exports Read list_namespaces Read list_data_items Read SIMILAR READ TOOLS ON OTHER SERVERS
list_bases Airtable list_tables Airtable list_records Airtable get_record Airtable search_records Airtable search Amplitude RELATED READING
FREQUENTLY ASKED QUESTIONS
What does the get_current_address tool do?
Get the address currently selected in Ghidra. It is categorised as a Read tool in the Ghidra MCP Server, which means it retrieves data without modifying state.
How do I enforce a policy on get_current_address?
Add a rule in your Intercept YAML policy under the tools section for get_current_address. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Ghidra MCP server.
What risk level is get_current_address?
get_current_address is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Can I rate-limit get_current_address?
Yes. Add a rate_limit block to the get_current_address rule in your Intercept 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 get_current_address completely?
Set action: deny in the Intercept policy for get_current_address. 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 get_current_address?
get_current_address is provided by the Ghidra MCP server (LaurieWired/GhidraMCP). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
ENFORCE POLICIES ON GHIDRA
Open source. One binary. Zero dependencies.