This record as markdown: /tools/bybit-exchange-trading-mcp/getlporderlist.md
What getLPOrderList does on Bybit MCP Server
AI agents call getLPOrderList 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 getLPOrderList is rated Low
This tool retrieves order data without modifying or executing trades. It is a read operation. Severity is medium rather than low because LP order data on a financial exchange could be sensitive and expose portfolio or position information, though retrieval alone carries no direct financial risk.
From the tool's definition Tool name 'getLPOrderList' and description 'Query the user' indicate a retrieval operation. The 'get' prefix and 'List' suffix are typical of read-only query tools.
Attacks that exploit this kind of access
The rule that runs getLPOrderList 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 getLPOrderList, this is the rule to start with:
getLPOrderList 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 getLPOrderList call is checked against it from then on.
Questions about getLPOrderList
Query the user. 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 getLPOrderList: 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.
getLPOrderList 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 getLPOrderList 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 getLPOrderList. 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.
getLPOrderList 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