Get all active trading pairs on ALEX AMM
AI agents call alex_get_trading_pairs 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 trading pair data from the ALEX AMM protocol. It performs a passive read operation that returns information without creating, modifying, deleting, or executing any transactions or code. The blast radius of misuse is minimal—an AI agent could only retrieve redundant data or flood queries, not cause financial loss, execute transactions, or damage data.
From the tool's definition Tool name contains 'get', description states 'Get all active trading pairs' — a retrieval operation with no side effects or state modification.
Attacks that exploit this kind of access
Get all active trading pairs on ALEX AMM. 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_trading_pairs: 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_trading_pairs 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_trading_pairs 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_trading_pairs. 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_trading_pairs 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 →