thesportsdb.teams.search
Search for a sports team by name across all sports (soccer, basketball, NFL, NHL, baseball, rugby, etc.). Returns team profile including sport type, primary league with league ID, stadium, location, country, founding year, website, and badge/logo URL. Use the returned league_id to retrieve past o...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/thesportsdb.teams.search.md
What thesportsdb.teams.search does on Apibase
AI agents call thesportsdb.teams.search 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 |
|---|---|---|---|
name | string | Yes | Team name to search for (e.g. "Arsenal", "Lakers", "New England Patriots"). Partial names are supported. |
Parameters from the server's own tool schema.
Why thesportsdb.teams.search is rated Low
Tool retrieves public sports team data without side effects, modifications, or access to sensitive information.
From the tool's definition Search for a sports team by name. Returns team profile including sport type, league, stadium, location, country, founding year, website, and badge/logo URL.
Attacks that exploit this kind of access
The rule that runs thesportsdb.teams.search 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.teams.search, this is the rule to start with:
thesportsdb.teams.search 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.teams.search call is checked against it from then on.
Questions about thesportsdb.teams.search
Search for a sports team by name across all sports (soccer, basketball, NFL, NHL, baseball, rugby, etc.). Returns team profile including sport type, primary league with league ID, stadium, location, country, founding year, website, and badge/logo URL. Use the returned league_id to retrieve past or upcoming match results via the events_past and events_next tools. 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.teams.search accepts 1 parameter: name. Required: name. 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.teams.search: 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.teams.search 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.teams.search 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.teams.search. 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.teams.search 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