analyze_binary

THE RISK

High Risk

Why analyze_binary needs a policy

This tool executes Ghidra's analysis engine on a user-supplied binary (PE, ELF, Mach-O, raw formats). It does more than read data — it actively runs Ghidra's analysis pipeline, which involves executing code analysis, disassembly, and potentially running Ghidra scripts/analyzers. Supplying a malicious or crafted binary could exploit the analysis toolchain.

From the tool's definition "Import and analyze a binary file with Ghidra" — triggers Ghidra's binary import and analysis pipeline against an arbitrary binary file

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

POLICY

How to control analyze_binary

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 analyze_binary:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "analyze_binary": {
      "limits": [
        {
          "counter": "analyze_binary_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

analyze_binary stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

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

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Kawaiidra MCP tools

Destructive cache_clear Clear cached analysis results. Can clear all cache or filter by binary/project. Destructive clear_comments Clear all comments (EOL, PRE, POST, PLATE) within a function Destructive delete_data_type Delete a user-defined data type from the binary. Destructive delete_function Delete a function by address or name. Removes the function definition but not the underlyi Destructive delete_label Delete a label/symbol at a specific address. Destructive remove_struct_field Remove a field from a structure by index. Execute run_script Execute arbitrary Jython code in the Ghidra scripting environment. Has access to currentPr Write add_enum_value Add a value to an existing enumeration.

All 94 Kawaiidra MCP tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Kawaiidra MCP → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about analyze_binary

What does the analyze_binary tool do? +

Import and analyze a binary file with Ghidra. Supports PE, ELF, Mach-O, and raw formats. It is categorised as a Execute tool in the Kawaiidra MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on analyze_binary? +

Register the Kawaiidra MCP server in PolicyLayer and add a rule for analyze_binary: 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 analyze_binary? +

analyze_binary is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit analyze_binary? +

Yes. Add a rate_limit block to the analyze_binary 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 analyze_binary completely? +

Set action: deny in the PolicyLayer policy for analyze_binary. 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 analyze_binary? +

analyze_binary 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.

CHECK YOUR STACK →