Set the current address context for subsequent operations. This is useful in headless mode to establish a working context. Address should be in hex format (e.g.,
AI agents use set_current_address to create or update resources in Kawaiidra MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kawaiidra MCP environment.
This tool modifies the current working context/state of the Ghidra session by setting an address pointer. It is a reversible state change (you can set a different address), not a destructive operation. It does not execute code, delete data, or have financial implications. It is a Write because it modifies the session state, though it does not create or alter binary analysis data itself.
From the tool's definition Set the current address context for subsequent operations
Documented attack patterns abuse exactly the kind of access set_current_address gives an agent:
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 set_current_address:
{
"version": "1",
"default": "deny",
"tools": {
"set_current_address": {
"limits": [
{
"counter": "set_current_address_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_current_address stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Set the current address context for subsequent operations. This is useful in headless mode to establish a working context. Address should be in hex format (e.g.,. It is categorised as a Write tool in the Kawaiidra MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Kawaiidra MCP server in PolicyLayer and add a rule for set_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.
set_current_address is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_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.
Set action: deny in the PolicyLayer policy for set_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.
set_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.
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.