get_assembly_info

Decompilation

Returns key metadata about a .NET assembly including its name, version, target framework, runtime version, signing status, and debug information availability. A lightweight reconnaissance tool for understanding what kind of binary you are working with before committing to a full decompilation.

Parameters

Parameter	Type	Required	Default	Description
assembly_path	string	Yes	—	Path to the .dll or .exe file

Example

MCP JSON

{
  "tool": "get_assembly_info",
  "arguments": {
    "assembly_path": "/path/to/MyApp.dll"
  }
}

Python

result = await client.call_tool("get_assembly_info", {
    "assembly_path": "/path/to/MyApp.dll",
})

Response

Returns a structured summary with:

• Name and Full Name — assembly identity
• Version — assembly version number
• Location — resolved file path
• Target Framework — .NET Framework, .NET Core, .NET 5+, etc.
• Runtime Version — CLR version the assembly was built against
• Is Signed — whether the assembly has a strong name signature
• Has Debug Info — whether PDB debugging information is available

Usage tips

• Use this as a quick first step before diving into list_types or decompile_assembly.
• The target framework tells you which .NET runtime the assembly expects, which affects API availability.
• Check is_signed for trust verification in security-sensitive contexts.
• If has_debug_info is true, consider using use_pdb_variable_names in decompilation for better readability.

Related tools

• get_metadata_summary — deeper metadata with type/method counts (uses dnfile, no ilspycmd needed)
• list_types — explore the assembly’s type structure
• decompile_assembly — full source code recovery