# 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).

Agent View of the PolicyLayer registry record for `list_events`. HTML page: https://policylayer.com/tools/dev-infersports-infersports/list-events

## Facts

- Tool: `list_events`
- Server: Infersports (`https://api.infersports.dev/mcp`) — https://policylayer.com/tools/dev-infersports-infersports.md
- Homepage: https://github.com/https://api.infersports.dev/mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 7 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `date` | string | yes |  |
| `limit` | integer | no |  |
| `sport` | object | no |  |
| `league` | object | no |  |
| `status` | object | no |  |
| `date_to` | object | no |  |
| `timezone` | object | no |  |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "list_events",
    "arguments": {
      "date": "<date>"
    }
  }
}
```

## 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 own definition: "Tool description states it 'List[s] the fixtures for a calendar day' and 'Read-only' is explicitly stated in the server description."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Infersports:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_events": {}
  }
}
```

## Other tools on Infersports (16)

- `compare_lines` — Read — https://policylayer.com/tools/dev-infersports-infersports/compare-lines.md
- `compare_prob` — Read — https://policylayer.com/tools/dev-infersports-infersports/compare-prob.md
- `explain_handicap` — Read — https://policylayer.com/tools/dev-infersports-infersports/explain-handicap.md
- `find_arbitrage` — Read — https://policylayer.com/tools/dev-infersports-infersports/find-arbitrage.md
- `find_match` — Read — https://policylayer.com/tools/dev-infersports-infersports/find-match.md
- `find_value` — Read — https://policylayer.com/tools/dev-infersports-infersports/find-value.md
- `get_match_odds` — Read — https://policylayer.com/tools/dev-infersports-infersports/get-match-odds.md
- `get_opening_line` — Read — https://policylayer.com/tools/dev-infersports-infersports/get-opening-line.md
- `get_result` — Read — https://policylayer.com/tools/dev-infersports-infersports/get-result.md
- `get_sharp_line` — Read — https://policylayer.com/tools/dev-infersports-infersports/get-sharp-line.md
- `list_bookmakers` — Read — https://policylayer.com/tools/dev-infersports-infersports/list-bookmakers.md
- `list_results` — Read — https://policylayer.com/tools/dev-infersports-infersports/list-results.md
- `list_today_matches` — Read — https://policylayer.com/tools/dev-infersports-infersports/list-today-matches.md
- `match_info` — Read — https://policylayer.com/tools/dev-infersports-infersports/match-info.md
- `scan_slate` — Read — https://policylayer.com/tools/dev-infersports-infersports/scan-slate.md
- `score_prob` — Read — https://policylayer.com/tools/dev-infersports-infersports/score-prob.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=dev-infersports-infersports · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/dev-infersports-infersports