getLPPoolList
Query available liquidity pools with optional filtering by tag and token.\nReturns pool information including addresses, supported tokens, APY, and TVL.\n\nAI agent can use this to help users discover and compare liquidity pools.\n\nAgent hint: Use this endpoint when user wants to browse availabl...
This record as markdown: /tools/bybit-exchange-trading-mcp/getlppoollist.md
What getLPPoolList does on Bybit MCP Server
AI agents call getLPPoolList to retrieve information from Bybit MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why getLPPoolList is rated Low
This tool retrieves and queries existing liquidity pool data (addresses, tokens, APY, TVL) with optional filtering. It has no side effects, does not modify any state, does not execute transactions, and does not move funds. It is purely informational, enabling users to discover and compare pools. This is a straightforward Read operation with minimal risk.
From the tool's definition Tool description states 'Query available liquidity pools' and 'Returns pool information' with no mention of creating, modifying, deleting, or moving funds. The verb 'Query' and action of browsing/discovering pools are read-only operations.
Attacks that exploit this kind of access
The rule that runs getLPPoolList safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Bybit MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For getLPPoolList, this is the rule to start with:
getLPPoolList 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 Bybit MCP Server, apply this rule, and every getLPPoolList call is checked against it from then on.
Questions about getLPPoolList
Query available liquidity pools with optional filtering by tag and token.\nReturns pool information including addresses, supported tokens, APY, and TVL.\n\nAI agent can use this to help users discover and compare liquidity pools.\n\nAgent hint: Use this endpoint when user wants to browse available LP pools or search for pools by token.\nFilter by tokenSymbol to find pools containing a specific token. It is categorised as a Read tool in the Bybit MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Bybit MCP Server MCP server in PolicyLayer and add a rule for getLPPoolList: 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 Bybit MCP Server. Nothing to install.
getLPPoolList 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 getLPPoolList 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 getLPPoolList. 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.
getLPPoolList is provided by the Bybit MCP Server MCP server (bybit-exchange/trading-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Bybit MCP Server, and thousands of servers like it.
This server
Across the catalogue