get_fee_info

What get_fee_info does on Binance MCP Server

AI agents call get_fee_info to retrieve information from Binance MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_fee_info is rated Low

The 'get_' prefix and naming convention strongly suggest this retrieves fee structure data (trading fees, withdrawal fees, etc.) without modifying state. Although the description is absent, the tool's position among other non-destructive getters (balance queries, order book reads) and the nature of fee data (informational, read-only) place it in the Read category with low severity.

From the tool's definition Tool name 'get_fee_info' with 'get_' prefix indicates data retrieval. Description is empty, but context shows this server handles fee-related queries alongside read operations like 'get_account_snapshot', 'get_balance', 'get_order_book'.

The rule that runs get_fee_info safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Binance MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_fee_info, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_fee_info": {}
  }
}

Questions about get_fee_info