getDeliveryPrice
Retrieve historical delivery (settlement) prices for expired futures and options contracts,\nincluding the final settlement price and delivery timestamp.\n\nUse this endpoint when you need to:\n- Look up the settlement price of a specific expired futures or options contract\n- Analyze historical ...
This record as markdown: /tools/bybit-exchange-trading-mcp/getdeliveryprice.md
What getDeliveryPrice does on Bybit MCP Server
AI agents call getDeliveryPrice 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 getDeliveryPrice is rated Low
This tool retrieves historical settlement price data for expired contracts. It performs read-only operations on past transactions with no capability to modify, create, delete, or execute any operations. The tool cannot move funds, execute trades, or trigger external actions. It is a straightforward data lookup utility for analytics and reconciliation purposes.
From the tool's definition Tool name 'getDeliveryPrice' and description explicitly states 'Retrieve historical delivery (settlement) prices' and 'Look up the settlement price' — operations that only query/retrieve existing data.
Attacks that exploit this kind of access
The rule that runs getDeliveryPrice 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 getDeliveryPrice, this is the rule to start with:
getDeliveryPrice 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 getDeliveryPrice call is checked against it from then on.
Questions about getDeliveryPrice
Retrieve historical delivery (settlement) prices for expired futures and options contracts,\nincluding the final settlement price and delivery timestamp.\n\nUse this endpoint when you need to:\n- Look up the settlement price of a specific expired futures or options contract\n- Analyze historical delivery prices for research or PnL reconciliation\n- Retrieve paginated delivery records across multiple expired contracts\n\nSupported Products: USDT futures, USDC futures, Inverse futures, Option\n\nSupports cursor-based pagination via. 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 getDeliveryPrice: 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.
getDeliveryPrice 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 getDeliveryPrice 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 getDeliveryPrice. 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.
getDeliveryPrice 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