thesportsdb.events.next
Get the next scheduled matches for a sports league, identified by its TheSportsDB league ID. Returns upcoming events with home/away teams, scheduled date, kickoff time, round number, venue, and team badge URLs. Status field indicates scheduling state (NS = not started, PPD = postponed). Common le...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/thesportsdb.events.next.md
What thesportsdb.events.next does on Apibase
AI agents call thesportsdb.events.next 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 |
|---|---|---|---|
league_id | string | Yes | TheSportsDB league ID to retrieve upcoming events for (e.g. "4328" for English Premier League, "4387" for NBA, "4391" for NFL). Obtain a league ID from team sea |
Parameters from the server's own tool schema.
Why thesportsdb.events.next is rated Low
Retrieves public sports league schedule data with no side effects or modifications.
From the tool's definition Get the next scheduled matches, returns upcoming events with teams and dates.
Attacks that exploit this kind of access
The rule that runs thesportsdb.events.next 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 thesportsdb.events.next, this is the rule to start with:
thesportsdb.events.next 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 thesportsdb.events.next call is checked against it from then on.
Questions about thesportsdb.events.next
Get the next scheduled matches for a sports league, identified by its TheSportsDB league ID. Returns upcoming events with home/away teams, scheduled date, kickoff time, round number, venue, and team badge URLs. Status field indicates scheduling state (NS = not started, PPD = postponed). Common league IDs: 4328 (English Premier League), 4387 (NBA), 4391 (NFL), 4380 (MLB), 4335 (Scottish Premier League). Obtain league IDs from team_search results (the league_id field). Data source: TheSportsDB — free public sports database, no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
thesportsdb.events.next accepts 1 parameter: league_id. Required: league_id. 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 thesportsdb.events.next: 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.
thesportsdb.events.next 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 thesportsdb.events.next 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 thesportsdb.events.next. 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.
thesportsdb.events.next 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