Get historical trades for specific pool token
AI agents call alex_get_historical_swaps to retrieve information from Stacks AI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves historical swap/trade data from a DeFi pool. It is a read-only operation that fetches existing information without creating, modifying, deleting, or executing any transactions. The verb 'get' and the focus on retrieving historical data confirm this is a Read category tool with low severity since it poses no risk of unintended state changes.
From the tool's definition Tool name 'alex_get_historical_swaps' and description 'Get historical trades for specific pool token' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get historical trades for specific pool token. It is categorised as a Read tool in the Stacks AI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Stacks AI MCP Server MCP server in PolicyLayer and add a rule for alex_get_historical_swaps: 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 Stacks AI MCP Server. Nothing to install.
alex_get_historical_swaps 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 alex_get_historical_swaps 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 alex_get_historical_swaps. 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.
alex_get_historical_swaps is provided by the Stacks AI MCP Server MCP server (stack-ai-mcp/stacks-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 →