Low Risk

get_current_address

Get the current address. In GUI mode, returns the user

How to control get_current_address ↓

What get_current_address does on Kawaiidra MCP

AI agents call get_current_address to retrieve information from Kawaiidra MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_current_address needs a policy

This tool retrieves the current address pointer or position in Ghidra's analysis context. It has no side effects—it only queries existing state. This is a straightforward Read category tool with low severity, as reading metadata about the current analysis position poses minimal risk even if called by an AI agent.

From the tool's definition Tool name 'get_current_address' and description 'Get the current address' indicate a query operation that retrieves state information without modification.

Documented attack patterns abuse exactly the kind of access get_current_address gives an agent:

How to control get_current_address

PolicyLayer is an MCP gateway — it sits between your AI agents and Kawaiidra MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_current_address:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_current_address": {}
  }
}

get_current_address is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Kawaiidra MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_current_address

What does the get_current_address tool do? +

Get the current address. In GUI mode, returns the user. It is categorised as a Read tool in the Kawaiidra MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_current_address? +

Register the Kawaiidra MCP server in PolicyLayer and add a rule for get_current_address: 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 Kawaiidra MCP. Nothing to install.

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 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 get_current_address completely? +

Set action: deny in the PolicyLayer 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 Kawaiidra MCP server (wagonbomb/kawaiidra-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Kawaiidra MCP tool call.

Start from Kawaiidra MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

94 Kawaiidra MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.