Compare two functions by showing a side-by-side diff of their decompiled code. Functions can be in the same or different binaries.
AI agents call diff_functions 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.
The diff_functions tool retrieves and presents decompiled code for comparison purposes. It performs analysis and visualization of existing data without modifying binaries, executing code, or triggering external operations. This is a pure read operation with minimal security risk, appropriate for reverse engineering analysis within Ghidra.
From the tool's definition Tool description states 'Compare two functions by showing a side-by-side diff of their decompiled code' — this is a retrieval and display operation with no modification or execution of binaries.
Documented attack patterns abuse exactly the kind of access diff_functions 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 diff_functions:
{
"version": "1",
"default": "deny",
"tools": {
"diff_functions": {}
}
} diff_functions 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.
Compare two functions by showing a side-by-side diff of their decompiled code. Functions can be in the same or different binaries. 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 diff_functions: 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.
diff_functions 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 diff_functions 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 diff_functions. 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.
diff_functions 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.