Get order book depth for a trading pair. Returns bids and asks with prices and quantities.
AI agents call get_orderbook to retrieve information from AsterDex MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query of market data. While the data is relevant to financial trading decisions, the tool itself does not execute trades, transfer funds, or modify any state. It is a passive market data retrieval mechanism similar to the sibling tools (get_klines, get_ticker_price, etc.).
From the tool's definition Tool retrieves 'order book depth for a trading pair' with 'bids and asks with prices and quantities' — purely a data query with no modification, execution, or financial transaction capability.
Attacks that exploit this kind of access
Get order book depth for a trading pair. Returns bids and asks with prices and quantities. It is categorised as a Read tool in the AsterDex MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AsterDex MCP Server MCP server in PolicyLayer and add a rule for get_orderbook: 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 MCP Server. Nothing to install.
get_orderbook 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_orderbook 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_orderbook. 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_orderbook is provided by the AsterDex MCP Server MCP server (solenyaresearch0000/asterdex-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 →