Query all OCBS (One-Click-Buy-Sell) fiat orders on Binance.US. OCBS allows direct fiat-to-crypto conversions. This endpoint retrieves your OCBS order history for fiat transactions (e.g., USD to BTC). Response includes: - total: Total number of OCBS orders - dataList: Array of orders with details ...
AI agents call binance_us_ocbs_orders to retrieve information from Binance US MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries historical fiat transaction data without side effects. Although it accesses financial transaction history on a cryptocurrency exchange, it performs only data retrieval with no ability to execute trades, move funds, or modify orders.
From the tool's definition Tool description states 'Query all OCBS fiat orders' and 'retrieves your OCBS order history'; response only includes read-only order details (quoteId, orderStatus, amounts, timestamps) with no modification, deletion, or execution capabilities.
Documented attack patterns abuse exactly the kind of access binance_us_ocbs_orders gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Binance US MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for binance_us_ocbs_orders:
{
"version": "1",
"default": "deny",
"tools": {
"binance_us_ocbs_orders": {}
}
} binance_us_ocbs_orders 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.
Query all OCBS (One-Click-Buy-Sell) fiat orders on Binance.US. OCBS allows direct fiat-to-crypto conversions. This endpoint retrieves your OCBS order history for fiat transactions (e.g., USD to BTC). Response includes: - total: Total number of OCBS orders - dataList: Array of orders with details Each order contains: - quoteId, orderId, orderStatus (SUCCESS/FAIL) - fromCoin/fromAmount: Source currency and amount - toCoin/toAmount: Destination currency and amount - feeCoin/feeAmount: Fee details - ratio: Exchange rate - createTime: Order timestamp. It is categorised as a Read tool in the Binance US MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Binance US MCP Server MCP server in PolicyLayer and add a rule for binance_us_ocbs_orders: 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 US MCP Server. Nothing to install.
binance_us_ocbs_orders 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_ocbs_orders 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_ocbs_orders. 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_ocbs_orders is provided by the Binance US MCP Server MCP server (nirholas/binance-us-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Binance US 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.
93 Binance US MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.