Get all StableSwap pool contract addresses
AI agents call bitflow_get_stableswap_pools 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 retrieves public blockchain data (pool contract addresses) without creating, modifying, deleting, or executing anything. It is a straightforward query operation analogous to 'list' or 'fetch' commands. While the server as a whole manages financial assets, this specific tool merely reads static contract information, posing minimal direct risk.
From the tool's definition Tool name and description indicate it 'Get[s] all StableSwap pool contract addresses' — a pure data retrieval operation with no modification, deletion, or side effects.
Attacks that exploit this kind of access
Get all StableSwap pool contract addresses. 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 bitflow_get_stableswap_pools: 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.
bitflow_get_stableswap_pools 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 bitflow_get_stableswap_pools 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 bitflow_get_stableswap_pools. 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.
bitflow_get_stableswap_pools 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 →