// SCAN REPORT

Binary MCP Server

59 tools. 11 can modify or destroy data without limits.

2 destructive tools with no built-in limits. Policy required.

Last updated: 11 Jun 2026

11 can modify or destroy data

48 read-only

59 tools total

Community server · catalogue entry verified 11/06/2026

How to control Binary MCP Server ↓

TOOL MAP

What Binary MCP Server exposes to your agents

Read (48) Write / Execute (4) Destructive / Financial (2)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Binary MCP Server tools

Destructive · High delete_session This tool destructively removes user-created session artifacts (likely Ghidra, x64dbg, or WinDbg debug sessions) without reversibility. Destructive · Medium clean_cache The name 'clean_cache' strongly implies deletion or purging of cached data, which would be an irreversible destructive action. Execute · High batch_decompile Based on sibling tools like 'decompile_dotnet_assembly' and 'decompile_dotnet_type', this tool likely performs batch decompilation of binaries using tools like Ghidra or ILSpyCmd. Execute · High start_analysis_session This tool initiates debugging and analysis sessions with powerful binary analysis frameworks.

11 of Binary MCP Server's 59 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Binary MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and Binary MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "delete_session": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "generate_yara_rule_from_session": {
    "limits": [
      {
        "counter": "generate_yara_rule_from_session_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "decompile_dotnet_assembly": {
    "limits": [
      {
        "counter": "decompile_dotnet_assembly_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Binary MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON BINARY →

Free to start. No card required.

FULL CATALOGUE

All 59 Binary MCP Server tools

DESTRUCTIVE 2 tools

Destructive delete_session Delete a saved session. Destructive clean_cache clean_cache

EXECUTE 2 tools

Execute batch_decompile batch_decompile Execute start_analysis_session start_analysis_session

WRITE 2 tools

Write generate_yara_rule_from_session generate_yara_rule_from_session Write save_session save_session

READ 48 tools

Read decompile_dotnet_assembly decompile_dotnet_assembly Read decompile_dotnet_type decompile_dotnet_type Read analyze_api_call_chains analyze_api_call_chains Read analyze_control_flow analyze_control_flow Read analyze_dotnet analyze_dotnet Read analyze_function_completeness analyze_function_completeness Read check_binary check_binary Read compute_similarity_hashes compute_similarity_hashes Read detect_dynamic_api_resolution detect_dynamic_api_resolution Read detect_loops detect_loops Read detect_malware_behaviors detect_malware_behaviors Read detect_packers detect_packers Read diff_binaries diff_binaries Read extract_embedded_binaries extract_embedded_binaries Read extract_iocs extract_iocs Read extract_iocs_with_context extract_iocs_with_context Read fid_match fid_match Read find_anti_analysis find_anti_analysis Read find_dead_code find_dead_code Read find_inlined_clones find_inlined_clones Read find_ioctl_handlers find_ioctl_handlers Read find_related_sessions find_related_sessions Read find_similar_functions find_similar_functions Read find_stack_strings find_stack_strings Read find_vtables find_vtables Read get_active_session Get information about the currently active session. Read get_dotnet_il get_dotnet_il Read get_dotnet_types get_dotnet_types Read get_function_callers get_function_callers Read get_function_complexity get_function_complexity Read get_function_hash get_function_hash Read get_param_sinks get_param_sinks Read get_pe_info get_pe_info Read get_review_package get_review_package Read get_session_summary Get a lightweight summary of a session without loading full data. Read get_switch_tables get_switch_tables Read inspect_authenticode inspect_authenticode Read list_sessions list_sessions Read quick_scan quick_scan Read scan_pseudocode scan_pseudocode Read search_dotnet_types search_dotnet_types Read vt_behavior vt_behavior Read vt_check_api Check if VirusTotal API is configured and working. Read vt_lookup vt_lookup Read vt_search vt_search Read diagnose_dotnet_setup Check .NET analysis tools installation status. Read diagnose_setup Run diagnostic checks on Ghidra installation and environment. Read export_iocs export_iocs

OTHER 5 tools

Other load_full_session load_full_session Other load_session_section load_session_section Other configure_auto_session configure_auto_session Other generate_report generate_report Other generate_yara_rule_from_strings generate_yara_rule_from_strings

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Binary MCP Server

Can an AI agent delete data through the Binary MCP Server MCP server? +

Yes. The Binary MCP Server server exposes 2 destructive tools including delete_session, clean_cache. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Binary MCP Server? +

The Binary MCP Server server has 2 write tools including generate_yara_rule_from_session, save_session. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Binary MCP Server.

How many tools does the Binary MCP Server MCP server expose? +

59 tools across 4 categories: Destructive, Execute, Read, Write. 48 are read-only. 11 can modify, create, or delete data.

How do I enforce a policy on Binary MCP Server? +

Register the Binary MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Binary MCP Server tool call.

Deterministic rules across all 59 Binary MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON BINARY →

Free to start. No card required.

59 Binary MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.