AI agents call get_recent_trades 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 publicly available trade data for analysis purposes. It performs a read-only query operation that does not create, modify, execute code, delete data, or engage in financial transactions. The data accessed is public market information. Risk is minimal as the tool cannot be misused to cause harm—worst case is excessive API calls or market reconnaissance, which are low-severity concerns.
From the tool's definition Tool name 'get_recent_trades' and description 'Get recent public trades for a symbol' indicate retrieval of historical/public market data with no side effects.
Attacks that exploit this kind of access
Get recent public trades for a symbol. 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_recent_trades: 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_recent_trades 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_recent_trades 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_recent_trades. 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_recent_trades 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 →