match_info
Get the basics for a match in ONE call: the score, whether it's live, when it kicks off, and who's favored. No betting knowledge needed — this answers "who's winning?", "what's the score?", "what time does Brazil play (in my timezone)?", "who's the favorite?". Returns the live score + match clock...
This record as markdown: /tools/dev-infersports-infersports/match-info.md
What match_info does on Infersports
AI agents call match_info 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 |
|---|---|---|---|
date | object | — | |
query | string | Yes | |
sport | object | — | |
timezone | object | — |
Parameters from the server's own tool schema.
Why match_info is rated Low
This tool only retrieves and displays factual match data (score, time, status, favored team probability). It produces no side effects, does not modify data, does not execute code or external operations, and does not involve financial transactions. It is a pure read operation within a read-only server context.
From the tool's definition Tool description explicitly states 'Read-only' server; tool retrieves match information: 'Get the basics for a match in ONE call: the score, whether it's live, when it kicks off, and who's favored' — all query/retrieval operations with 'no betting knowledge…
Attacks that exploit this kind of access
The rule that runs match_info 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 match_info, this is the rule to start with:
match_info 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 match_info call is checked against it from then on.
Questions about match_info
Get the basics for a match in ONE call: the score, whether it's live, when it kicks off, and who's favored. No betting knowledge needed — this answers "who's winning?", "what's the score?", "what time does Brazil play (in my timezone)?", "who's the favorite?". Returns the live score + match clock, the status, the kickoff time (in timezone if you pass an IANA name like "America/New_York"), the favored team with a plain win probability (de-vigged from the 1x2 line), and a ready-to-read summary you can quote directly. Args: query: natural-language fixture or team, e.g. "Brazil vs Argentina" or just "Brazil". timezone: optional IANA timezone (e.g. "America/New_York", "Asia/Shanghai") for the kickoff time; default UTC. sport: optional filter — "football" or "basketball". date: optional UTC date "YYYY-MM-DD" to disambiguate same-name fixtures. On an ambiguous query, status is "ambiguous" and ask_user carries a prompt — do not guess. favorite is best-effort (null when no 1x2 is on file for the fixture). It is categorised as a Read tool in the Infersports MCP Server, which means it retrieves data without modifying state.
match_info accepts 4 parameters: date, query, sport, timezone. Required: query. 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 match_info: 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.
match_info 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 match_info 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 match_info. 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.
match_info 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