sports.bdl.games
Get NBA and NFL game results by date — scores, teams, status (Final/In Progress/Scheduled). Filter by date, season, or team. Covers all NBA and NFL games with real-time scores (BallDontLie)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/sports.bdl.games.md
What sports.bdl.games does on Apibase
AI agents call sports.bdl.games 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 | — | Game date (YYYY-MM-DD, e.g. "2026-03-29"). Returns all games on that date |
limit | integer | — | Max results (1-25, default 10) |
sport | string | — | Sport league: "nba" (default) or "nfl" |
season | integer | — | Season year (e.g. 2025 for 2025-26 season) |
team_id | integer | — | Filter by team ID (get IDs from bdl.teams) |
Parameters from the server's own tool schema.
Why sports.bdl.games is rated Low
Retrieves historical sports data with no side effects, modifications, or external operations.
From the tool's definition Get NBA and NFL game results, scores, status. Filter by date, season, or team.
Attacks that exploit this kind of access
The rule that runs sports.bdl.games 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.bdl.games, this is the rule to start with:
sports.bdl.games 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.bdl.games call is checked against it from then on.
Questions about sports.bdl.games
Get NBA and NFL game results by date — scores, teams, status (Final/In Progress/Scheduled). Filter by date, season, or team. Covers all NBA and NFL games with real-time scores (BallDontLie). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
sports.bdl.games accepts 5 parameters: date, limit, sport, season, team_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 sports.bdl.games: 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.bdl.games 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.bdl.games 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.bdl.games. 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.bdl.games 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