Get historical kline/candlestick data for Bitcoin
AI agents call get_bitcoin_price_history to retrieve information from Binance Bitcoin MCP Tool without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool purely retrieves and queries historical price data from Binance with no side effects. It does not create, modify, delete, execute code, or commit financial transactions. The data returned is read-only market information.
From the tool's definition Tool description states it retrieves 'historical kline/candlestick data for Bitcoin' and server description emphasizes 'historical Bitcoin market data' and 'price history.' The sibling tools (get_bitcoin_order_book, get_bitcoin_recent_trades,…
Attacks that exploit this kind of access
Get historical kline/candlestick data for Bitcoin. It is categorised as a Read tool in the Binance Bitcoin MCP Tool MCP Server, which means it retrieves data without modifying state.
Register the Binance Bitcoin MCP Tool MCP server in PolicyLayer and add a rule for get_bitcoin_price_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 Binance Bitcoin MCP Tool. Nothing to install.
get_bitcoin_price_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 get_bitcoin_price_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 get_bitcoin_price_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.
get_bitcoin_price_history is provided by the Binance Bitcoin MCP Tool MCP server (milescool/binance-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →