⚙️ 交易所信息查询 - 交易规则和限制说明 🔍 功能说明： 获取Binance交易所的基本信息和交易规则，包括支持的交易对、最小下单量、价格数量精度、手续费规则、API限制等详细信息。是进行程序化交易和风控设置的基础参考。 ⚠️ 重要提醒： • 实时更新：交易规则可能随时调整，建议定期查询 • 精度要求：下单时必须严格遵守价格和数量精度规则 • 限制条件：包含最小下单量、最大下单量、单笔限额等 • API限速：注意请求频率限制，避免触发风控 🎯 适用场景： • 程序化交易系统获取交易对配置信息 • 风控系统设置订单参数验证规则 • 交易员了解新交易对的交易限制 • 合规人员确认交易...
AI agents call binance_exchange_info to retrieve information from Binance without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries static or slowly-changing reference data about exchange configuration. It has no capability to execute trades, modify accounts, or cause any state changes. Even though it's foundational for trading systems, the tool itself only performs information lookup operations, making it a Read category with low severity.
From the tool's definition Tool description explicitly states it 'gets Binance exchange basic information and trading rules' (获取Binance交易所的基本信息和交易规则), including 'supported trading pairs, minimum order quantities, price precision, fee rules, API limits' — all read-only queries with no…
Documented attack patterns abuse exactly the kind of access binance_exchange_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Binance, and nothing reaches the server without passing your rules. This is the rule we recommend for binance_exchange_info:
{
"version": "1",
"default": "deny",
"tools": {
"binance_exchange_info": {}
}
}binance_exchange_info 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.
⚙️ 交易所信息查询 - 交易规则和限制说明 🔍 功能说明： 获取Binance交易所的基本信息和交易规则，包括支持的交易对、最小下单量、价格数量精度、手续费规则、API限制等详细信息。是进行程序化交易和风控设置的基础参考。 ⚠️ 重要提醒： • 实时更新：交易规则可能随时调整，建议定期查询 • 精度要求：下单时必须严格遵守价格和数量精度规则 • 限制条件：包含最小下单量、最大下单量、单笔限额等 • API限速：注意请求频率限制，避免触发风控 🎯 适用场景： • 程序化交易系统获取交易对配置信息 • 风控系统设置订单参数验证规则 • 交易员了解新交易对的交易限制 • 合规人员确认交易规则和监管要求 📋 输出示例： 查询成功后将返回： \. It is categorised as a Read tool in the Binance MCP Server, which means it retrieves data without modifying state.
Register the Binance MCP server in PolicyLayer and add a rule for binance_exchange_info: 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 Binance. Nothing to install.
binance_exchange_info 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 binance_exchange_info 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 binance_exchange_info. 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.
binance_exchange_info is provided by the Binance MCP server (kydlikebtc/binance-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Binance, 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.
35 Binance tools catalogued and risk-classified — across an index of 43,000+ MCP servers.