binance_us_cust_new_order
Place a new trade order through the custodial solution. ⚠️ REQUIRES CUSTODIAL SOLUTION API KEY Supported order types: - LIMIT: Requires timeInForce, quantity, price - MARKET: Requires quantity OR quoteOrderQty - STOP_LOSS: Requires quantity, stopPrice (executes as MARKET when triggered) - STOP_LO...
This record as markdown: /tools/nirholas-binance-mcp/binance-us-cust-new-order.md
What binance_us_cust_new_order does on Binance MCP Server
AI agents use binance_us_cust_new_order to commit financial operations through Binance MCP Server, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why binance_us_cust_new_order is rated Critical
This tool places live trade orders on the Binance exchange, directly committing financial obligations by buying or selling cryptocurrency. Misuse could result in significant financial loss through unauthorized or erroneous trades, making this a critical financial risk.
From the tool's definition Place a new trade order through the custodial solution... execute orders... spot trading... crypto assets
Attacks that exploit this kind of access
The rule that runs binance_us_cust_new_order 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 binance_us_cust_new_order, this is the rule to start with:
Any call to binance_us_cust_new_order is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Binance MCP Server, apply this rule, and every binance_us_cust_new_order call is checked against it from then on.
Questions about binance_us_cust_new_order
Place a new trade order through the custodial solution. ⚠️ REQUIRES CUSTODIAL SOLUTION API KEY Supported order types: - LIMIT: Requires timeInForce, quantity, price - MARKET: Requires quantity OR quoteOrderQty - STOP_LOSS: Requires quantity, stopPrice (executes as MARKET when triggered) - STOP_LOSS_LIMIT: Requires timeInForce, quantity, price, stopPrice - TAKE_PROFIT: Requires quantity, stopPrice (executes as MARKET when triggered) - TAKE_PROFIT_LIMIT: Requires timeInForce, quantity, price, stopPrice - LIMIT_MAKER: Requires quantity, price (POST-ONLY order) ExpressTrade Feature: When allowExpressTrade=true and custodial sub-account balance is insufficient, the full amount will be automatically transferred from the custodial partner. Response includes: symbol, orderId, status, type, side, price, quantity, executedQty, and expressTradeFlag. It is categorised as a Financial tool in the Binance MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Binance MCP Server MCP server in PolicyLayer and add a rule for binance_us_cust_new_order: 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 MCP Server. Nothing to install.
binance_us_cust_new_order is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the binance_us_cust_new_order 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_cust_new_order. 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_cust_new_order is provided by the Binance MCP Server MCP server (nirholas/binance-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Binance MCP Server, and thousands of servers like it.
Across the catalogue