List functions and their successors (call tree).
AI agents call Radare2_list_functions_tree to retrieve information from Reversecore_MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs static binary analysis by reading and organizing function information into a call tree structure. It queries existing analysis results without side effects, code execution, or data modification. While part of a reverse engineering suite, the specific operation is fundamentally a retrieval/query operation.
From the tool's definition Tool retrieves and displays function call tree data without modifying binaries or executing arbitrary code. Description indicates it 'lists' functions and their successors (call tree), a read-only analysis operation.
Attacks that exploit this kind of access
List functions and their successors (call tree). It is categorised as a Read tool in the Reversecore_MCP MCP Server, which means it retrieves data without modifying state.
Register the Reversecore_ MCP server in PolicyLayer and add a rule for Radare2_list_functions_tree: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Reversecore_MCP. Nothing to install.
Radare2_list_functions_tree is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the Radare2_list_functions_tree rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for Radare2_list_functions_tree. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
Radare2_list_functions_tree is provided by the Reversecore_ MCP server (sjkim1127/reversecore_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →