sportsdb_search_teams
Search teams by name. Returns matching teams with basic info, badges, and stadium details.
This record as markdown: /tools/io-github-lacausecrypto-sports-hub/sportsdb-search-teams.md
What sportsdb_search_teams does on Sports Hub
AI agents call sportsdb_search_teams to retrieve information from Sports Hub without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why sportsdb_search_teams is rated Low
The tool searches for and returns publicly available sports data (team information, badges, stadium details) with no side effects. It is a standard read/retrieval operation consistent with other sibling tools like apifootball_get_leagues and apifootball_get_players. The severity is low because misuse would only expose existing public sports data, with no capability to modify, delete, or cause operational damage.
From the tool's definition Tool performs search and retrieval operations: 'Search teams by name. Returns matching teams with basic info, badges, and stadium details.' This is purely a query operation that retrieves data without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
The rule that runs sportsdb_search_teams safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sports Hub, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sportsdb_search_teams, this is the rule to start with:
sportsdb_search_teams 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 Sports Hub, apply this rule, and every sportsdb_search_teams call is checked against it from then on.
Questions about sportsdb_search_teams
Search teams by name. Returns matching teams with basic info, badges, and stadium details. It is categorised as a Read tool in the Sports Hub MCP Server, which means it retrieves data without modifying state.
Register the Sports Hub MCP server in PolicyLayer and add a rule for sportsdb_search_teams: 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 Sports Hub. Nothing to install.
sportsdb_search_teams 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 sportsdb_search_teams 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 sportsdb_search_teams. 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.
sportsdb_search_teams is provided by the Sports Hub MCP server (mcp-sports-hub). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sports Hub, and thousands of servers like it.
This server
Across the catalogue