getNewDeliveryPrice
Retrieve historical option delivery prices grouped by base coin and settlement coin,\nreturned in reverse chronological order (most recent settlement first).\n\nUse this endpoint when you need to:\n- Look up recent option settlement prices by base coin (BTC, ETH, etc.) without knowing specific co...
This record as markdown: /tools/bybit-exchange-trading-mcp/getnewdeliveryprice.md
What getNewDeliveryPrice does on Bybit MCP Server
AI agents call getNewDeliveryPrice 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 getNewDeliveryPrice is rated Low
This tool performs a read-only query of historical option delivery price data. It has no side effects, does not execute trades, move funds, or modify any data. The retrieval of settlement history and delivery prices is a passive data lookup operation typical of market data queries.
From the tool's definition Retrieve historical option delivery prices grouped by base coin and settlement coin, returned in reverse chronological order (most recent settlement first). The tool description explicitly states it retrieves/looks up data without modifying state.
Attacks that exploit this kind of access
The rule that runs getNewDeliveryPrice 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 getNewDeliveryPrice, this is the rule to start with:
getNewDeliveryPrice 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 getNewDeliveryPrice call is checked against it from then on.
Questions about getNewDeliveryPrice
Retrieve historical option delivery prices grouped by base coin and settlement coin,\nreturned in reverse chronological order (most recent settlement first).\n\nUse this endpoint when you need to:\n- Look up recent option settlement prices by base coin (BTC, ETH, etc.) without knowing specific contract symbols\n- Retrieve the latest delivery price shortly after settlement completes\n- Access settlement history for a specific base coin / settlement coin pair\n\nSupported Products: Option only\n\nDo not use this endpoint for futures delivery prices — use. 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 getNewDeliveryPrice: 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.
getNewDeliveryPrice 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 getNewDeliveryPrice 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 getNewDeliveryPrice. 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.
getNewDeliveryPrice 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