list_data
AI agents call list_data 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.
Despite the empty description, the naming pattern and sibling tools strongly indicate this retrieves or enumerates data without modification. Binary analysis tools like decompile, disassemble, and get_* operations are read-only examination functions. List operations have no side effects on the binary being analyzed. Confidence is moderate due to missing description, but the contextual evidence is clear.
From the tool's definition Tool name 'list_data' suggests listing/retrieving data items, consistent with sibling tools like 'list_data_items', 'list_classes', and 'list_entities' which are query operations on binary analysis artifacts.
Attacks that exploit this kind of access
list_data. 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_data: 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_data 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_data 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_data. 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_data 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 →