get_match_odds
Get all current odds for a match across bookmakers. Args: event_id: event id from find_match / list_today_matches (e.g. "evt_…"). markets: optional filter — any of "1x2", "asian_handicap", "totals". bookmakers: optional filter — bookmaker keys, e.g. ["pinnacle", "crown"]. period: optional — "full...
This record as markdown: /tools/dev-infersports-infersports/get-match-odds.md
What get_match_odds does on Infersports
AI agents call get_match_odds to retrieve information from Infersports without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
format | string | — | |
period | object | — | |
markets | object | — | |
event_id | string | Yes | |
bookmakers | object | — |
Parameters from the server's own tool schema.
Why get_match_odds is rated Low
This tool retrieves and queries betting odds data without modifying, deleting, or executing any operations. It accepts an event_id and optional filters to return odds information in various formats. No side effects occur—it is a pure data retrieval operation consistent with Read category tools like 'get' and 'fetch'.
From the tool's definition Tool description explicitly states 'Get all current odds for a match across bookmakers' with parameters for filtering and formatting existing odds data. Server description confirms 'Read-only' nature.
Attacks that exploit this kind of access
The rule that runs get_match_odds safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Infersports, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_match_odds, this is the rule to start with:
get_match_odds 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 Infersports, apply this rule, and every get_match_odds call is checked against it from then on.
Questions about get_match_odds
Get all current odds for a match across bookmakers. Args: event_id: event id from find_match / list_today_matches (e.g. "evt_…"). markets: optional filter — any of "1x2", "asian_handicap", "totals". bookmakers: optional filter — bookmaker keys, e.g. ["pinnacle", "crown"]. period: optional — "full_time" or "half_time" (default: both). format: odds format — decimal | hk | malay | american | indonesian | probability. It is categorised as a Read tool in the Infersports MCP Server, which means it retrieves data without modifying state.
get_match_odds accepts 5 parameters: format, period, markets, event_id, bookmakers. Required: event_id. The full parameter table on this page comes from the server's own tool schema.
Register the Infersports MCP server in PolicyLayer and add a rule for get_match_odds: 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 Infersports. Nothing to install.
get_match_odds 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 get_match_odds 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 get_match_odds. 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.
get_match_odds is provided by the Infersports MCP server (https://api.infersports.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Infersports, and thousands of servers like it.
This server
Across the catalogue