sports.bdl.players
Search NBA players by name — returns position, jersey number, and current team. Example: "lebron" → LeBron James #23 F, Los Angeles Lakers (BallDontLie)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/sports.bdl.players.md
What sports.bdl.players does on Apibase
AI agents call sports.bdl.players 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 |
|---|---|---|---|
limit | integer | — | Max results (1-25, default 10) |
search | string | — | Search by player name (e.g. "lebron", "curry", "mahomes") |
team_id | integer | — | Filter by team ID |
Parameters from the server's own tool schema.
Why sports.bdl.players is rated Low
Retrieves public player information without side effects or data modification.
From the tool's definition Search NBA players by name — returns position, jersey number, current team
Attacks that exploit this kind of access
The rule that runs sports.bdl.players 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.players, this is the rule to start with:
sports.bdl.players 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.players call is checked against it from then on.
Questions about sports.bdl.players
Search NBA players by name — returns position, jersey number, and current team. Example: "lebron" → LeBron James #23 F, Los Angeles Lakers (BallDontLie). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
sports.bdl.players accepts 3 parameters: limit, search, 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.players: 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.players 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.players 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.players. 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.players 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