// SCAN REPORT

x64dbg MCP Server

39 tools. 16 can modify or destroy data without limits.

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

Last updated: 29 Jun 2026

16 can modify or destroy data

23 read-only

39 tools total

Community server · catalogue entry verified 29/06/2026

How to control x64dbg MCP Server ↓

TOOL MAP

What x64dbg MCP Server exposes to your agents

Read (23) Write / Execute (13) Destructive / Financial (2)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous x64dbg MCP Server tools

Destructive · High close_debugger This tool irreversibly terminates all active debugger sessions and kills processes. Destructive · High terminate_session Terminating a process is an irreversible action; any unsaved state in the debuggee is permanently lost. Execute · High execute_command This tool directly executes arbitrary commands in a debugging context where side effects depend entirely on the command arguments provided by the user. Execute · High step_out This tool triggers execution of code within a debugged Windows process until a specific control flow point (function return).

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

POLICY

How to control x64dbg MCP Server

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

Deny destructive operations

{
  "close_debugger": {
    "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

{
  "create_minidump": {
    "limits": [
      {
        "counter": "create_minidump_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "analyze_function": {
    "limits": [
      {
        "counter": "analyze_function_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 x64dbg 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 X64DBG →

Instant setup, no code required.

FULL CATALOGUE

All 39 x64dbg MCP Server tools

DESTRUCTIVE 2 tools

Destructive close_debugger Terminate all sessions and kill all tracked x64dbg/x32dbg processes. Destructive terminate_session Stop the debuggee process and close the debugging session.

EXECUTE 11 tools

Execute attach_to_process Attach to a running process by PID and create a debugging session. Execute collect_bp_args Loop: continue execution → hit breakpoint → read a memory expression → repeat N times. Execute continue_execution Resume a paused debuggee. Runs until the next breakpoint, exception, manual pause, or process exit. Execute detach_session Detach the debugger from the process without killing it — the target process continues running. Execute execute_command Execute a raw x64dbg script command synchronously and return its console output. Execute load_executable START HERE. Load a PE executable (.exe or .dll) and create a debugging session. Execute pause_execution Interrupt a running debuggee. No-op if already paused — returns current state immediately. Execute step_into Single-step N instructions, following CALL instructions into callees. Execute step_out Run until the current function returns (executes to its matching RET instruction). Execute step_over Single-step N instructions, treating each CALL as a single step (does not enter callees). Execute write_memory Patch bytes in the debuggee

WRITE 2 tools

Write create_minidump Create a Windows minidump (.dmp) of the debuggee process for offline analysis. Write save_memory_dump Dump a raw memory region from the debuggee to a file on disk.

READ 23 tools

Read analyze_function Analyze a function: boundaries, size, instruction count, call graph, and isLeaf flag. Read analyze_suspicious_apis Cross-reference the module Read check_section_anomalies Check PE sections for structural anomalies. Read detect_anti_debug Scan the module for common anti-debugging techniques. Read detect_packing Scan a PE module for signs of packing or obfuscation. Read disassemble Disassemble instructions starting at an address or symbol. Read find_strings Find ASCII and Unicode strings in the debuggee Read generate_security_report START HERE for malware triage. Run all four security checks in parallel and produce a consolidated report. Read get_call_stack Get the call stack (backtrace) of the current thread. REQUIRES: state= Read get_cross_references Find all cross-references (xrefs) to or from an address. Read get_exports List exported functions/symbols from a PE module Read get_imports List imported functions for a module: importing DLL name, function name, ordinal, IAT address. Read get_memory_map List all virtual memory regions of the debuggee process: Read get_modules List all modules (main EXE + loaded DLLs): name, path, base address, size, entry point, sections. Read get_pe_header Parse the PE header of a loaded module. Read get_registers Read CPU register values of the active thread. REQUIRES: state= Read get_status Query the current session/debugger state. Always safe — never changes debugger state. Read get_threads List all threads in the debuggee process: TID, handle, entry address, TEB, state, priority, name. Read list_functions List all recognized functions in the debuggee: address, name, size, module. Read list_sessions List all active debugging sessions: id, state, pid, architecture, executable, breakpointCount. Read read_memory Read raw bytes from the debuggee Read search_memory Search the debuggee Read wait_for_state Block until the session reaches a target state, then return a full snapshot.

OTHER 1 tools

Other my_tool my_tool

EXPLORE

Related servers

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

FAQ

Questions about x64dbg MCP Server

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

Yes. The x64dbg MCP Server server exposes 2 destructive tools including close_debugger, terminate_session. 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 x64dbg MCP Server? +

The x64dbg MCP Server server has 2 write tools including create_minidump, save_memory_dump. 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 x64dbg MCP Server.

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

39 tools across 3 categories: Execute, Read, Write. 23 are read-only. 16 can modify, create, or delete data.

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

Register the x64dbg 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 x64dbg MCP Server tool call.

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

ENFORCE POLICY ON X64DBG →

Instant setup, no code required.

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