List functions in a binary
AI agents call list_functions to retrieve information from Binary Ninja Cline MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool queries and returns information about functions present in a binary file without executing code, modifying data, or triggering side effects. This is characteristic of Read category tools. Severity is low because listing functions is informational only and poses minimal risk even if misused by an agent.
From the tool's definition Tool name 'list_functions' and description 'List functions in a binary' indicate a retrieval operation with no modification or execution of code. This is a query operation that retrieves metadata about binary structure.
Attacks that exploit this kind of access
List functions in a binary. It is categorised as a Read tool in the Binary Ninja Cline MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Binary Ninja Cline MCP Server MCP server in PolicyLayer and add a rule for list_functions: 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 Binary Ninja Cline MCP Server. Nothing to install.
list_functions 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 list_functions 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 list_functions. 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.
list_functions is provided by the Binary Ninja Cline MCP Server MCP server (opensensor/bn_cline_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 →