binance_place_order
Place a market or limit buy/sell order. Requires BINANCE_API_KEY + BINANCE_SECRET_KEY.
This record as markdown: /tools/nirholas-agenti/binance-place-order.md
What binance_place_order does on Agenti
AI agents use binance_place_order to commit financial operations through Agenti, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why binance_place_order is rated Critical
This tool directly places buy or sell orders on Binance, which constitutes committing real financial transactions in cryptocurrency markets. Misuse could result in significant financial loss through unintended trades. It falls squarely in the Financial category, which is the most severe applicable category.
From the tool's definition Place a market or limit buy/sell order
Attacks that exploit this kind of access
The rule that runs binance_place_order safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Agenti, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For binance_place_order, this is the rule to start with:
Any call to binance_place_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 Agenti, apply this rule, and every binance_place_order call is checked against it from then on.
Questions about binance_place_order
Place a market or limit buy/sell order. Requires BINANCE_API_KEY + BINANCE_SECRET_KEY. It is categorised as a Financial tool in the Agenti MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Agenti MCP server in PolicyLayer and add a rule for binance_place_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 Agenti. Nothing to install.
binance_place_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_place_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_place_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_place_order is provided by the Agenti MCP server (nirholas/agenti). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Agenti, and thousands of servers like it.
Across the catalogue