list_events
List the fixtures for a calendar day — or a bounded [date, date_to] range. Unlike list_today_matches (today + anything still live), this is a strict window for whatever date you ask for. Pass date_to (inclusive, max 31 days after date) to cover a whole tournament window in ONE call — "all group-s...
This record as markdown: /tools/dev-infersports-infersports/list-events.md
What list_events does on Infersports
AI agents call list_events 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 | string | Yes | |
limit | integer | — | |
sport | object | — | |
league | object | — | |
status | object | — | |
date_to | object | — | |
timezone | object | — |
Parameters from the server's own tool schema.
Why list_events is rated Low
This tool purely retrieves fixture scheduling data within a bounded date range. It has no side effects, does not modify data, does not execute code or external operations, and does not involve financial transactions. The server itself is explicitly marked "Read-only," confirming the safe retrieval nature of all its tools including this one.
From the tool's definition Tool description states it "List[s] the fixtures for a calendar day" and "Read-only" is explicitly stated in the server description.
Attacks that exploit this kind of access
The rule that runs list_events 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 list_events, this is the rule to start with:
list_events 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 list_events call is checked against it from then on.
Questions about list_events
List the fixtures for a calendar day — or a bounded [date, date_to] range. Unlike list_today_matches (today + anything still live), this is a strict window for whatever date you ask for. Pass date_to (inclusive, max 31 days after date) to cover a whole tournament window in ONE call — "all group-stage matches June 11–28" needs no per-day loop. UTC is canonical: pass an IANA timezone and the day boundaries are computed in that zone (so "June 12 in Shanghai" excludes a match that is still June 11 / already June 13 locally); each fixture keeps its UTC scheduled_at and adds scheduled_at_local. Capped to limit (truncated flags overflow) — narrow with sport/status/league rather than paging. Args: date: REQUIRED calendar day "YYYY-MM-DD" (e.g. "2026-06-12") — the window start. date_to: optional inclusive end day "YYYY-MM-DD" (max 31 days after date); omit for a single day. timezone: optional IANA timezone (e.g. "Asia/Shanghai", "America/New_York") for the day boundary; default is the UTC day. sport: optional filter — "football" or "basketball". status: optional filter — "scheduled", "live" or "finished". league: optional league filter — a name (fuzzy-matched, e.g. "World Cup") or an external id ("lg_…"). limit: max fixtures to return (1–200, default 50). It is categorised as a Read tool in the Infersports MCP Server, which means it retrieves data without modifying state.
list_events accepts 7 parameters: date, limit, sport, league, status, date_to, timezone. Required: date. 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 list_events: 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.
list_events 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 list_events 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 list_events. 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.
list_events 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