call-sites
Call Sites
Find function call sites in a binary.
When to use
- Find all locations where a specific function is called
- Identify callers of a function
- Check if a function contains calls to other specific functions
- Filter call sites based on caller criteria
Instructions
List function calls
Using the VulHunt MCP tools, open the project (open_project) and run the following Lua query (query_project) to get all the function calls:
local calls = project:calls_matching{
to = <target_call>,
}
local results = {}
for _, call in ipairs(calls) do
table.insert(results, {
caller_address = tostring(call.caller_address),
call_address = tostring(call.call_address),
})
end
return results
Possible values for <target_call>:
- A string, e.g.
"system" - An AddressValue
- VulHunt APIs return addresses as AddressValue instances
- Create one with
AddressValue.new(<hex_addr>)(e.g.,<hex_addr> = 0x1234)
- A regex, e.g.
{matching = "<regex>", kind = "symbol"} - A byte pattern, e.g.
{matching = "41544155", kind = "bytes"}
Returns a JSON object containing:
caller_addressis the address of the function that makes the callcall_addressis the address of the call site (specifically, the code block address where the call is made)
List function calls with criteria
To restrict the search to function calls where the caller also contains other calls, or the caller is a specific function, use:
local calls = project:calls_matching{
to = <target_call>,
where = function(caller)
return caller:named("<name>") and caller:has_call(<target_call>)
end
}
List function calls in a certain function
To verify whether a certain function calls another function, run:
local f = project:functions(<target_function>)
local has_call = f:has_call(<target_call>)
return tostring(has_call)
The returned function object contains these fields:
f.name,f.address,f.total_bytes
To get the list of call-sites within a function, run:
local f = project:functions(<target_function>)
local calls = f:calls(<target_call>)
local call_addresses = {}
for _, c in ipairs(calls) do
table.insert(call_addresses, tostring(c))
end
return call_addresses
Possible values for <target_function>:
- A string, e.g.
"system" - An AddressValue
- VulHunt APIs return addresses as an AddressValue
- To build an AddressValue, use for example:
AddressValue.new(0x1234)
- A regex, e.g.
{matching = "<regex>", kind = "symbol", all = true} - A byte pattern, e.g.
{matching = "41544155", kind = "bytes", all = true}
allis a boolean. If set totrue, it returns a table containing all matching functions. Iffalse(default), it returns only the first matching value. The for loop is not necessary if the function target is only one (i.e.allis not set to true)
References
- calls-matching-param.md - Input format for
calls_matching - calls-matching-table.md - Structure of the returned table from
calls_matching
URLs to additional documentation pages are available at https://vulhunt.re/llm.txt
Related Skills
- functions (
/functions) - Use this skill first to find and list functions before analyzing their call sites - dataflow-analysis (
/dataflow-analysis) - For advanced call analysis with taint tracking and data flow between function parameters and arguments - decompiler (
/decompiler) - View decompiled code of caller functions to better understand the calling context
More from vulhunt-re/skills
decompiler
Decompile a function to C-like pseudocode for human-readable analysis. Use to understand function logic, review control flow, or prepare for code pattern matching.
16functions
Find and list functions in a binary by name, address, regex, or byte pattern. Use as the starting point for binary analysis, to locate specific functions, or to enumerate all functions matching criteria.
6btp-ba2-cli
Interact with the Binarly Transparency Platform (BTP) via CLI commands for uploading firmware, running scans, downloading BA2 archives, and pushing custom rules. Use when you need to interact with the Binarly Transparency Platform or working with BA2s.
6code-pattern-matching
Search for code patterns in decompiled output using Weggli semantic matching. Use when finding vulnerable code constructs like unchecked memcpy, buffer operations, or specific function call patterns in pseudocode.
6dataflow-analysis
Track data flow between function parameters, calls, and arguments using taint analysis. Use when detecting vulnerabilities like command injection, buffer overflows, or tracing user input to dangerous functions.
6byte-pattern-matching
Search for raw byte patterns (hex sequences, opcodes) in binary code. Use when looking for specific instruction sequences, machine code patterns, UEFI SMI handlers, or known vulnerability signatures by their byte representation.
5