List all variables (parameters, local variables, return type) of a function with their types, storage locations, and sizes.
AI agents call get_function_variables 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.
This tool retrieves and queries metadata about variables within a function during binary analysis—parameters, local variables, return types, and storage information. It is purely informational with no side effects on the binary, the Ghidra database, or any external system. This is a standard read operation typical of reverse engineering tools.
From the tool's definition Tool description states it 'List all variables' of a function with their types, storage locations, and sizes. The verb 'list' and the focus on retrieval of function metadata with no modification indicated.
Documented attack patterns abuse exactly the kind of access get_function_variables 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 get_function_variables:
{
"version": "1",
"default": "deny",
"tools": {
"get_function_variables": {}
}
} get_function_variables is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all variables (parameters, local variables, return type) of a function with their types, storage locations, and sizes. It is categorised as a Read tool in the Kawaiidra MCP MCP Server, which means it retrieves data without modifying state.
Register the Kawaiidra MCP server in PolicyLayer and add a rule for get_function_variables: 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.
get_function_variables 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_function_variables 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_function_variables. 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_function_variables 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.