getPredictionMatchList
Query all matches for a sports event with their current status and prediction market info.\n\nReturns match details including teams, scheduled time, match status (Live/Upcoming/Ended),\nand associated prediction markets for each match.\n\nAI agent can use this to show the user available matches t...
This record as markdown: /tools/bybit-exchange-trading-mcp/getpredictionmatchlist.md
What getPredictionMatchList does on Bybit MCP Server
AI agents call getPredictionMatchList 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 getPredictionMatchList is rated Low
This tool queries and retrieves prediction market information for sports events. It has no side effects, does not modify data, does not execute code or commands, does not delete anything, and does not move money. The primary action is data retrieval ('Query', 'Returns', 'get all matches') which aligns with the Read category.
From the tool's definition Query all matches for a sports event with their current status and prediction market info. Returns match details including teams, scheduled time, match status, and associated prediction markets. Tool retrieves and displays data without modifying state.
Attacks that exploit this kind of access
The rule that runs getPredictionMatchList 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 getPredictionMatchList, this is the rule to start with:
getPredictionMatchList 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 getPredictionMatchList call is checked against it from then on.
Questions about getPredictionMatchList
Query all matches for a sports event with their current status and prediction market info.\n\nReturns match details including teams, scheduled time, match status (Live/Upcoming/Ended),\nand associated prediction markets for each match.\n\nAI agent can use this to show the user available matches to bet on,\nand then use the eventId to get detailed market info before trading.\n\nAgent hint: Use this to get all matches for FIFA 2026 (eventType=1).\nEach match has an associated eventId — use it with getPredictionEventDetail to get tokenIds.\nFilter by matchStatus: 1=Live, 2=Upcoming, 3=Ended.\nDo NOT show Ended matches for trading unless the user explicitly asks. 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 getPredictionMatchList: 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.
getPredictionMatchList 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 getPredictionMatchList 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 getPredictionMatchList. 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.
getPredictionMatchList 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