Low Risk

getOrderList

Query the user

How to control getOrderList ↓

What getOrderList does on Bybit MCP Server

AI agents call getOrderList to retrieve information from Bybit MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why getOrderList needs a policy

This tool retrieves order information from the Bybit exchange. The name and context (among trading/positions tools) indicate it performs a data query operation with no side effects. Even though the description is vague ('Query the user'), the tool name and server context strongly suggest this fetches order list data for read purposes only.

From the tool's definition Tool name 'getOrderList' indicates data retrieval. Description states 'Query the user' which is uninformative but suggests a read operation (querying/fetching order data).

Documented attack patterns abuse exactly the kind of access getOrderList gives an agent:

How to control getOrderList

PolicyLayer is an MCP gateway — it sits between your AI agents and Bybit MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for getOrderList:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "getOrderList": {}
  }
}

getOrderList is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Bybit MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about getOrderList

What does the getOrderList tool do? +

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.

How do I enforce a policy on getOrderList? +

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

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

Can I rate-limit getOrderList? +

Yes. Add a rate_limit block to the getOrderList 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 getOrderList completely? +

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

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

Enforce policy on every Bybit MCP Server tool call.

Start from Bybit MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

326 Bybit MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.