sports.football.fixtures
Football/soccer fixtures, live scores, and results — filter by date, league (Premier League, La Liga, Champions League...), team. 2000+ leagues, 171 countries. 362+ fixtures per day (API-Sports)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/sports.football.fixtures.md
What sports.football.fixtures does on Apibase
AI agents call sports.football.fixtures to retrieve information from Apibase 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 | — | Date in YYYY-MM-DD format (e.g. "2026-03-20"). Returns all fixtures for that day. |
live | boolean | — | Set to true to get only live/in-play fixtures |
team | integer | — | Team ID to filter fixtures |
league | integer | — | League ID (e.g. 39 = Premier League, 140 = La Liga, 78 = Bundesliga) |
season | integer | — | Season year (e.g. 2025) |
Parameters from the server's own tool schema.
Why sports.football.fixtures is rated Low
Retrieves sports fixture data and scores; no side effects or data modification.
From the tool's definition fixtures, live scores, results — filter by date, league, team
Attacks that exploit this kind of access
The rule that runs sports.football.fixtures safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sports.football.fixtures, this is the rule to start with:
sports.football.fixtures 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 Apibase, apply this rule, and every sports.football.fixtures call is checked against it from then on.
Questions about sports.football.fixtures
Football/soccer fixtures, live scores, and results — filter by date, league (Premier League, La Liga, Champions League...), team. 2000+ leagues, 171 countries. 362+ fixtures per day (API-Sports). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
sports.football.fixtures accepts 5 parameters: date, live, team, league, season. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for sports.football.fixtures: 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 Apibase. Nothing to install.
sports.football.fixtures 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 sports.football.fixtures 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 sports.football.fixtures. 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.
sports.football.fixtures is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue