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...
Risk signalsAccepts freeform code/query input (query)
Part of the Infersports server.
Free to start. No card required.
AI agents call match_info to retrieve information from Infersports without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though match_info only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"match_info": {}
}
}See the full Infersports policy for all 14 tools.
These attack patterns abuse exactly the kind of access match_info gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
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.
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.
Deterministic rules across all 14 Infersports tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.