Get older market historical trades.
AI agents call historicalTrades to retrieve information from Aster Finance MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves past trade data from the exchange for analysis purposes. It has no side effects—it does not create, modify, delete, or execute orders/transactions. While it is part of a financial trading platform, reading historical market data does not commit financial obligations or move money.
From the tool's definition Tool name 'historicalTrades' and description 'Get older market historical trades' indicate a query operation that retrieves historical market data without modification, deletion, or financial transaction execution.
Attacks that exploit this kind of access
Get older market historical trades. It is categorised as a Read tool in the Aster Finance MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Aster Finance MCP Server MCP server in PolicyLayer and add a rule for historicalTrades: 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 Aster Finance MCP Server. Nothing to install.
historicalTrades 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 historicalTrades 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 historicalTrades. 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.
historicalTrades is provided by the Aster Finance MCP Server MCP server (questflowai/aster-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 →