AI agents call list_filename to retrieve information from Binaryninja without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and enumerates file names already open in the Binary Ninja session. It performs no side effects, does not execute code, modify data, or delete anything. The blast radius of misuse is minimal — an AI agent could only learn which files are open, which is low-impact information disclosure.
From the tool's definition Tool description states 'List file names of all opened files' — a pure query operation with no modification or execution.
Documented attack patterns abuse exactly the kind of access list_filename gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Binaryninja, and nothing reaches the server without passing your rules. This is the rule we recommend for list_filename:
{
"version": "1",
"default": "deny",
"tools": {
"list_filename": {}
}
}list_filename is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List file names of all opened files. It is categorised as a Read tool in the Binaryninja MCP Server, which means it retrieves data without modifying state.
Register the Binaryninja MCP server in PolicyLayer and add a rule for list_filename: 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 Binaryninja. Nothing to install.
list_filename 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_filename 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_filename. 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_filename is provided by the Binaryninja MCP server (mcpphalanx/binaryninja-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Binaryninja, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
16 Binaryninja tools catalogued and risk-classified — across an index of 43,000+ MCP servers.