getLPPoolInfo

SERVERBybit MCP Server SOURCEbybit-exchange/trading-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/bybit-exchange-trading-mcp/getlppoolinfo.md

WHAT IT DOES

What getLPPoolInfo does on Bybit MCP Server

AI agents call getLPPoolInfo 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.

RISK

Why getLPPoolInfo is rated Low

This tool retrieves and queries existing pool information without creating, modifying, deleting, or executing operations. It is purely informational, returning data about liquidity pools to inform user decisions. No side effects occur from calling this endpoint—it is a safe read operation with minimal blast radius if misused by an AI agent.

From the tool's definition Tool description explicitly states it 'Query[s] detailed pool information' and 'Get[s] complete details' about pools.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs getLPPoolInfo 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 getLPPoolInfo, this is the rule to start with:

getLPPoolInfo Allowed

getLPPoolInfo is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "getLPPoolInfo": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Bybit MCP Server, apply this rule, and every getLPPoolInfo call is checked against it from then on.

FAQ

Questions about getLPPoolInfo

What does the getLPPoolInfo tool do? +

Query detailed pool information including APY breakdown, fees, token reserves,\nand historical performance.\n\nUse this after selecting a pool from the pool list to get complete details.\n\nAgent hint: Use this endpoint when user wants detailed information about a specific pool.\nCall this before staking to show the user complete pool details.\npoolAddress is required and must come from getLPPoolList. It is categorised as a Read tool in the Bybit MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on getLPPoolInfo? +

Register the Bybit MCP Server MCP server in PolicyLayer and add a rule for getLPPoolInfo: 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.

What risk level is getLPPoolInfo? +

getLPPoolInfo is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit getLPPoolInfo? +

Yes. Add a rate_limit block to the getLPPoolInfo 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.

How do I block getLPPoolInfo completely? +

Set action: deny in the PolicyLayer policy for getLPPoolInfo. 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.

What MCP server provides getLPPoolInfo? +

getLPPoolInfo 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.

KEEP EXPLORING

More on Bybit MCP Server, and thousands of servers like it.

This server

All 380 Bybit MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →