List exported functions/symbols with pagination.
AI agents call list_exports 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.
This tool retrieves static information about a binary's exported functions and symbols. It performs no side effects, does not execute code, modify data, or trigger external operations. It is purely informational analysis, consistent with other sibling tools like 'list_classes', 'list_data', and 'get_binary_info' which are all Read category operations.
From the tool's definition Tool name 'list_exports' and description 'List exported functions/symbols with pagination' indicate querying/retrieving data about binary exports without modification or execution.
Attacks that exploit this kind of access
List exported functions/symbols with pagination. 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_exports: 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_exports 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_exports 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_exports. 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_exports 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 →