Get a list of supported OTC (Over-The-Counter) trading pairs on Binance.US. OTC trading allows large block trades to be executed outside the regular order book, minimizing market impact. This endpoint returns available coin pairs with their minimum and maximum trading limits. Response includes: -...
AI agents call binance_us_otc_coin_pairs to retrieve information from Sperax Ecosystem Crypto & DeFI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool queries and retrieves data about available trading pairs and their limits from Binance.US. It does not execute trades, move funds, create positions, or modify any state. Even though the context involves cryptocurrency and the example mentions 'Convert large amounts of BTC to USDT,' the tool itself only provides read-only market information. The actual execution of a trade would require a separate tool.
From the tool's definition Tool name 'binance_us_otc_coin_pairs' and description state it 'Get a list of supported OTC trading pairs' and 'returns available coin pairs with their minimum and maximum trading limits.' This is purely informational retrieval with no side effects.
Documented attack patterns abuse exactly the kind of access binance_us_otc_coin_pairs gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Sperax Ecosystem Crypto & DeFI MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for binance_us_otc_coin_pairs:
{
"version": "1",
"default": "deny",
"tools": {
"binance_us_otc_coin_pairs": {}
}
}binance_us_otc_coin_pairs 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 a list of supported OTC (Over-The-Counter) trading pairs on Binance.US. OTC trading allows large block trades to be executed outside the regular order book, minimizing market impact. This endpoint returns available coin pairs with their minimum and maximum trading limits. Response includes: - fromCoin/toCoin: The trading pair - fromCoinMinAmount/fromCoinMaxAmount: Min/max amounts for the sell coin - toCoinMinAmount/toCoinMaxAmount: Min/max amounts for the buy coin Example: Convert large amounts of BTC to USDT without affecting market price. It is categorised as a Read tool in the Sperax Ecosystem Crypto & DeFI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Sperax Ecosystem Crypto & DeFI MCP Server MCP server in PolicyLayer and add a rule for binance_us_otc_coin_pairs: 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 Sperax Ecosystem Crypto & DeFI MCP Server. Nothing to install.
binance_us_otc_coin_pairs 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_us_otc_coin_pairs 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_us_otc_coin_pairs. 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_us_otc_coin_pairs is provided by the Sperax Ecosystem Crypto & DeFI MCP Server MCP server (sperax/sperax-crypto-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Sperax Ecosystem Crypto & DeFI 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.
1318 Sperax Ecosystem Crypto & DeFI MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.