getPredictionPriceHistory
Query historical price data for prediction outcome tokens.\nReturns price time series for chart display.\n\nTwo modes:\n1. By tokenIds: specify up to 20 token IDs directly\n2. By eventId: specify an event to get price history for all its tokens\n\nThe
This record as markdown: /tools/bybit-exchange-trading-mcp/getpredictionpricehistory.md
What getPredictionPriceHistory does on Bybit MCP Server
AI agents call getPredictionPriceHistory 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 getPredictionPriceHistory is rated Low
This tool retrieves historical pricing data for prediction tokens with no modification or side effects. It is a read-only query operation that returns data for display purposes. The two modes (tokenIds or eventId) are both retrieval parameters. No creation, modification, deletion, code execution, or financial transactions occur.
From the tool's definition Query historical price data for prediction outcome tokens. Returns price time series for chart display.
Attacks that exploit this kind of access
The rule that runs getPredictionPriceHistory 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 getPredictionPriceHistory, this is the rule to start with:
getPredictionPriceHistory 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 getPredictionPriceHistory call is checked against it from then on.
Questions about getPredictionPriceHistory
Query historical price data for prediction outcome tokens.\nReturns price time series for chart display.\n\nTwo modes:\n1. By tokenIds: specify up to 20 token IDs directly\n2. By eventId: specify an event to get price history for all its tokens\n\nThe. 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 getPredictionPriceHistory: 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.
getPredictionPriceHistory 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 getPredictionPriceHistory 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 getPredictionPriceHistory. 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.
getPredictionPriceHistory 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