binance_get_trade_history
Get recent filled trades for a symbol. Requires BINANCE_API_KEY + BINANCE_SECRET_KEY.
This record as markdown: /tools/nirholas-agenti/binance-get-trade-history.md
What binance_get_trade_history does on Agenti
AI agents call binance_get_trade_history to retrieve information from Agenti without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why binance_get_trade_history is rated Low
This tool retrieves and queries trade history data from Binance with no side effects. It does not create, modify, delete, execute code, or move funds. While the broader server enables cryptocurrency transactions, this specific tool is narrowly scoped to data retrieval only.
From the tool's definition Tool description states 'Get recent filled trades for a symbol' - this is a retrieval operation that queries historical trade data without modifying or executing any actions.
Attacks that exploit this kind of access
The rule that runs binance_get_trade_history 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_get_trade_history, this is the rule to start with:
binance_get_trade_history is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Agenti, apply this rule, and every binance_get_trade_history call is checked against it from then on.
Questions about binance_get_trade_history
Get recent filled trades for a symbol. Requires BINANCE_API_KEY + BINANCE_SECRET_KEY. It is categorised as a Read tool in the Agenti MCP Server, which means it retrieves data without modifying state.
Register the Agenti MCP server in PolicyLayer and add a rule for binance_get_trade_history: 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_get_trade_history 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_get_trade_history 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_get_trade_history. 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_get_trade_history 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.
This server
Across the catalogue