thesportsdb.events.past

SERVERApibase SOURCEapibase-mcp-client

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/thesportsdb.events.past.md

WHAT IT DOES

What thesportsdb.events.past does on Apibase

AI agents call thesportsdb.events.past 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 past events for (e.g. "4328" for English Premier League, "4387" for NBA, "4391" for NFL). Obtain a league ID from team search

Parameters from the server's own tool schema.

RISK

Why thesportsdb.events.past is rated Low

Retrieves historical sports event data with no side effects or modification capabilities.

From the tool's definition Get the most recent completed match results for a sports league. Returns match events with scores, dates, venues.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs thesportsdb.events.past 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.past, this is the rule to start with:

thesportsdb.events.past Allowed

thesportsdb.events.past is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "thesportsdb.events.past": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every thesportsdb.events.past call is checked against it from then on.

FAQ

Questions about thesportsdb.events.past

What does the thesportsdb.events.past tool do? +

Get the most recent completed match results for a sports league, identified by its TheSportsDB league ID. Returns match events with home/away teams, scores, round number, date, time, venue, and result string. 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.

What parameters does thesportsdb.events.past accept? +

thesportsdb.events.past accepts 1 parameter: league_id. Required: league_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on thesportsdb.events.past? +

Register the Apibase MCP server in PolicyLayer and add a rule for thesportsdb.events.past: 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.

What risk level is thesportsdb.events.past? +

thesportsdb.events.past is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit thesportsdb.events.past? +

Yes. Add a rate_limit block to the thesportsdb.events.past 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.

How do I block thesportsdb.events.past completely? +

Set action: deny in the PolicyLayer policy for thesportsdb.events.past. 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.

What MCP server provides thesportsdb.events.past? +

thesportsdb.events.past 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.

KEEP EXPLORING

More on Apibase, and thousands of servers like it.

This server

All 1384 Apibase tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →