Low Risk

binance_get_trade_history

Get recent filled trades for a symbol. Requires BINANCE_API_KEY + BINANCE_SECRET_KEY.

How to control binance_get_trade_history ↓

AI agents call binance_get_trade_history to retrieve information from Agenti without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

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.

Documented attack patterns abuse exactly the kind of access binance_get_trade_history gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Agenti, and nothing reaches the server without passing your rules. This is the rule we recommend for binance_get_trade_history:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "binance_get_trade_history": {}
  }
}

binance_get_trade_history is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Agenti — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the binance_get_trade_history tool do? +

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.

How do I enforce a policy on binance_get_trade_history? +

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.

What risk level is binance_get_trade_history? +

binance_get_trade_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit binance_get_trade_history? +

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.

How do I block binance_get_trade_history completely? +

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.

What MCP server provides binance_get_trade_history? +

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.

Enforce policy on every Agenti tool call.

Deterministic rules across all 73 Agenti tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

73 Agenti tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.