// SCAN REPORT

Ida Domain

74 tools. 24 can modify or destroy data without limits.

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

Last updated: 11 Jun 2026

24 can modify or destroy data

50 read-only

74 tools total

Community server · catalogue entry verified 11/06/2026

How to control Ida Domain ↓

TOOL MAP

What Ida Domain exposes to your agents

Read (50) Write / Execute (21) Destructive / Financial (3)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Ida Domain tools

Destructive · High dbg_delete_bp Deleting breakpoints is an irreversible modification of debugging state. Destructive · High delete_stack The tool performs deletion of data (stack variables) that cannot be easily recovered or undone within the IDA Pro analysis context. Destructive · High close_database Closing the IDA database and terminating the worker process is irreversible in the context of the session — any unsaved analysis, changes, or state will be lost. Execute · High callgraph The tool performs an active operation (graph building/analysis) rather than simple retrieval.

24 of Ida Domain's 74 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Ida Domain

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

Deny destructive operations

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

{
  "apply_types": {
    "limits": [
      {
        "counter": "apply_types_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "decompile": {
    "limits": [
      {
        "counter": "decompile_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 Ida Domain — 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 IDA DOMAIN →

Free to start. No card required.

FULL CATALOGUE

All 74 Ida Domain tools

DESTRUCTIVE 3 tools

Destructive dbg_delete_bp Delete breakpoints Destructive delete_stack Delete stack vars Destructive close_database Close the project's IDA database and terminate its worker process.

EXECUTE 13 tools

Execute callgraph Build call graph starting from root functions Execute dbg_run_to Run to address Execute dbg_start Start debugger Execute py_eval Execute Python code in IDA context Execute dbg_continue Continue debugger Execute dbg_exit Exit debugger Execute dbg_step_into Step into Execute dbg_step_over Step over Execute infer_types Infer types Execute dbg_enable_bp Enable/disable breakpoints Execute dbg_write_mem Write debug memory Execute open_database open_database Execute patch_asm Patch assembly instructions at addresses

WRITE 8 tools

Write apply_types Apply types (function/global/local/stack) Write dbg_add_bp Add breakpoints Write declare_stack Create stack vars Write declare_type Declare types Write patch Patch bytes at memory addresses with hex data Write rename Unified rename operation for functions, globals, locals, and stack variables Write set_comments Set comments at addresses (both disassembly and decompiler views) Write upload_binary Load a binary file from the local disk to the server for analysis.

READ 50 tools

Read decompile Decompile functions to pseudocode Read analyze_funcs Comprehensive function analysis: decompilation, xrefs, callees, strings, constants, blocks Read analyze_strings analyze_strings Read basic_blocks basic_blocks Read callees Get all functions called by the specified functions Read callers Get all functions that call the specified functions Read cursor_addr Get current address Read cursor_func Get current function Read dbg_callstack Get call stack Read dbg_current_gpregs Get current thread GP registers Read dbg_current_regs Get specific current thread registers Read dbg_gpregs_thread Get GP registers for threads Read dbg_list_bps List breakpoints Read dbg_read_mem Read debug memory Read dbg_regs Get all registers Read dbg_regs_cur Get current thread registers Read dbg_regs_for_thread Get specific thread registers Read dbg_regs_thread Get thread registers Read disasm disasm Read entrypoints Get entry points Read find_bytes find_bytes Read find_insn_operands find_insn_operands Read find_insns find_insns Read find_paths Find execution paths between source and target addresses Read get_bytes Read bytes from memory addresses Read get_global_value Read global variable values by address or name Read get_string Read strings from memory addresses Read get_u16 Read 16-bit unsigned integers from memory addresses Read get_u32 Read 32-bit unsigned integers from memory addresses Read get_u64 Read 64-bit unsigned integers from memory addresses Read get_u8 Read 8-bit unsigned integers from memory addresses Read idb_meta Get IDB metadata Read imports List imports Read list_funcs List functions Read list_globals List globals Read local_types List local types Read lookup_funcs Get functions by address or name (auto-detects) Read read_struct Read struct fields Read search search Read search_structs Search structs Read segments List all segments Read stack_frame Get stack vars Read strings List strings Read struct_info Get struct info Read structs List all structures Read xref_matrix Build matrix showing cross-references between entities Read xrefs_to Get all cross-references to specified addresses Read xrefs_to_field Get cross-references to structure fields Read export_funcs Export function data in various formats Read int_convert Convert numbers to different formats

EXPLORE

Related servers

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

FAQ

Questions about Ida Domain

Can an AI agent delete data through the Ida Domain MCP server? +

Yes. The Ida Domain server exposes 3 destructive tools including dbg_delete_bp, delete_stack, close_database. 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 Ida Domain? +

The Ida Domain server has 8 write tools including apply_types, dbg_add_bp, declare_stack. 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 Ida Domain.

How many tools does the Ida Domain MCP server expose? +

74 tools across 4 categories: Destructive, Execute, Read, Write. 50 are read-only. 24 can modify, create, or delete data.

How do I enforce a policy on Ida Domain? +

Register the Ida Domain 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 Ida Domain tool call.

Deterministic rules across all 74 Ida Domain tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON IDA DOMAIN →

Free to start. No card required.

74 Ida Domain tools catalogued and risk-classified — across an index of 43,000+ MCP servers.