AI agents call get_spot_market_data 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 retrieves real-time market data (prices, statistics, order book depth, available pairs) with no side effects. It performs a read-only query operation that does not create, modify, delete, or execute any trades or commands. The severity is low because reading public market data poses minimal risk even if an AI agent calls it repeatedly or with arbitrary parameters.
From the tool's definition Tool name 'get_spot_market_data' and description 'Get spot market data: prices, 24h stats, orderbook, or all trading pairs' indicate retrieval of market information without modification or execution of trades.
Attacks that exploit this kind of access
Get spot market data: prices, 24h stats, orderbook, or all trading pairs. 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_spot_market_data: 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_spot_market_data 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_spot_market_data 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_spot_market_data. 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_spot_market_data 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 →