AI agents call get_function_hash to retrieve information from Binary MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to read/compute metadata about functions (hashes for similarity analysis, checksums, etc.) without causing side effects. Consistent with 'compute_similarity_hashes' sibling tool. No capability to execute code, modify binaries, delete data, or commit financial transactions. Confidence is moderate (0.8) due to empty description, but the name and server context strongly suggest a Read classification.
From the tool's definition Tool name 'get_function_hash' suggests retrieving or computing a hash value from a function, consistent with analysis/inspection capabilities.
Documented attack patterns abuse exactly the kind of access get_function_hash gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Binary MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_function_hash:
{
"version": "1",
"default": "deny",
"tools": {
"get_function_hash": {}
}
}get_function_hash 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_function_hash. It is categorised as a Read tool in the Binary MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Binary MCP Server MCP server in PolicyLayer and add a rule for get_function_hash: 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 MCP Server. Nothing to install.
get_function_hash 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_function_hash 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_function_hash. 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_function_hash is provided by the Binary MCP Server MCP server (sarks0/binary-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Binary MCP Server, 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.
59 Binary MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.