find_dead_code

THE RISK

Low Risk

Why find_dead_code needs a policy

This tool retrieves and reports information about code structure within a binary without modifying, executing, or destructively altering anything. It performs static analysis to discover unused functions—a read-only reconnaissance operation typical of reverse engineering workflows. No code execution, data modification, or irreversible actions occur.

From the tool's definition Tool performs analysis and identification of unreachable functions by examining cross-references (xrefs). Description uses verbs 'find', 'identify' with no modification, deletion, execution, or side effects on the binary or system.

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

POLICY

How to control find_dead_code

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "find_dead_code": {}
  }
}

find_dead_code is read-only, so it stays allowed — but 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.

CAP 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 Execute analyze_binary Import and analyze a binary file with Ghidra. Supports PE, ELF, Mach-O, and raw formats.

All 94 Kawaiidra MCP tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about find_dead_code

What does the find_dead_code tool do? +

Find unreachable or orphaned functions — functions with no callers (xrefs to). Helps identify unused code, compiler artifacts, or hidden functionality. 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 find_dead_code? +

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

find_dead_code is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit find_dead_code? +

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

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

find_dead_code 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 →