get_iris_liquidity_pools
Get liquidity pools from Iris, optionally filtered by tokens or DEX
This record as markdown: /tools/indigoprotocol-indigo-mcp/get-iris-liquidity-pools.md
What get_iris_liquidity_pools does on Indigo Protocol MCP
AI agents call get_iris_liquidity_pools to retrieve information from Indigo Protocol MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
dex | string | — | DEX name filter |
tokenA | string | — | First token identifier |
tokenB | string | — | Second token identifier |
Parameters from the server's own tool schema.
Why get_iris_liquidity_pools is rated Low
This tool queries and retrieves liquidity pool information without creating, modifying, or deleting data. It has no execution of code, financial transactions, or destructive operations. Standard read operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool retrieves liquidity pool data from Iris with optional filtering; no modifications or side effects described. Action verbs 'Get' and 'filtered' indicate read-only query operation.
Attacks that exploit this kind of access
The rule that runs get_iris_liquidity_pools safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Indigo Protocol MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_iris_liquidity_pools, this is the rule to start with:
get_iris_liquidity_pools is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Indigo Protocol MCP, apply this rule, and every get_iris_liquidity_pools call is checked against it from then on.
Questions about get_iris_liquidity_pools
Get liquidity pools from Iris, optionally filtered by tokens or DEX. It is categorised as a Read tool in the Indigo Protocol MCP MCP Server, which means it retrieves data without modifying state.
get_iris_liquidity_pools accepts 3 parameters: dex, tokenA, tokenB. The full parameter table on this page comes from the server's own tool schema.
Register the Indigo Protocol MCP server in PolicyLayer and add a rule for get_iris_liquidity_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 Indigo Protocol MCP. Nothing to install.
get_iris_liquidity_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 get_iris_liquidity_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 get_iris_liquidity_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.
get_iris_liquidity_pools is provided by the Indigo Protocol MCP server (indigoprotocol/indigo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Indigo Protocol, and thousands of servers like it.
This server
Across the catalogue