AI agents call get_binance_oi_history to retrieve information from Asterdex 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 open interest data from Binance. It has no side effects, does not execute trades, modify positions, or affect financial state. The analysis use cases mentioned (trend confirmation, short accumulation detection) are informational only. Classification as Read is appropriate for a data-fetching utility.
From the tool's definition Tool name 'get_binance_oi_history' and description 'Get Binance open interest history' indicate data retrieval with no modification or execution capabilities. Returns historical market data for analysis purposes only.
Attacks that exploit this kind of access
Get Binance open interest history. Shows money flowing in/out over time. Rising OI + rising price = trend confirmation. Rising OI + falling price = short accumulation. It is categorised as a Read tool in the Asterdex MCP Server, which means it retrieves data without modifying state.
Register the Asterdex MCP server in PolicyLayer and add a rule for get_binance_oi_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 Asterdex. Nothing to install.
get_binance_oi_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_binance_oi_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_binance_oi_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_binance_oi_history is provided by the Asterdex MCP server (tyranosurasmax/asterdex-mcp-server). 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 →