Get recent trades for a trading pair on Binance.US. Returns trade ID, price, quantity, time, and maker/taker info.
AI agents call binance_us_recent_trades to retrieve information from BNB Chain MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a data retrieval operation with no side effects. While it relates to financial markets, it does not move money, commit financial obligations, or execute trades—it merely provides read-only access to past trade records. The most severe category applicable is Read.
From the tool's definition Tool retrieves recent trade data (trade ID, price, quantity, time, maker/taker info) for a trading pair on Binance.US. No modification, execution, deletion, or financial transaction occurs—it only queries and returns historical trading information.
Documented attack patterns abuse exactly the kind of access binance_us_recent_trades gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and BNB Chain MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for binance_us_recent_trades:
{
"version": "1",
"default": "deny",
"tools": {
"binance_us_recent_trades": {}
}
}binance_us_recent_trades 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.
Get recent trades for a trading pair on Binance.US. Returns trade ID, price, quantity, time, and maker/taker info. It is categorised as a Read tool in the BNB Chain MCP MCP Server, which means it retrieves data without modifying state.
Register the BNB Chain MCP server in PolicyLayer and add a rule for binance_us_recent_trades: 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 BNB Chain MCP. Nothing to install.
binance_us_recent_trades 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_recent_trades 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_recent_trades. 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_recent_trades is provided by the BNB Chain MCP server (nirholas/bnbchain-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 1240 BNB Chain MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
1240 BNB Chain MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.