AI agents call get_functions to retrieve information from BinAssistMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves static metadata (function list) from a binary without executing code, modifying data, or causing side effects. It is purely informational, analogous to listing directory contents. The blast radius if misused by an agent is minimal—it only exposes structural information about the binary that could inform further analysis but cannot directly harm systems or data.
From the tool's definition Tool name 'get_functions' and description 'Get list of all functions in the binary' indicate a query/retrieval operation with no modification or execution of code. This is a straightforward data retrieval task typical of binary analysis exploration.
Documented attack patterns abuse exactly the kind of access get_functions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and BinAssistMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_functions:
{
"version": "1",
"default": "deny",
"tools": {
"get_functions": {}
}
}get_functions 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.
Get list of all functions in the binary. It is categorised as a Read tool in the BinAssistMCP MCP Server, which means it retrieves data without modifying state.
Register the BinAssist MCP server in PolicyLayer and add a rule for get_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 BinAssistMCP. Nothing to install.
get_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 get_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 get_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.
get_functions is provided by the BinAssist MCP server (symgraph/binassistmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 44 BinAssistMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
44 BinAssistMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.