Find players by name (full or partial) and resolve them to player keys. This is the way to turn a name the user typed into the player_key that get_player_stats, analyze_player_stats, add_drop_player, and set_lineup need. Returns name, position, eligible positions, injury status, and ownership (fr...
AI agents call search_players to retrieve information from Yahoo Fantasy Baseball without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Player name to search for; full or partial |
count | integer | — | Number of players to return (max 25) |
start | integer | — | Pagination offset |
status | string | — | Availability filter: A=available (free agents + waivers), FA=free agents, W=on waivers, T=taken (rostered). Omit to search all players. |
position | string | — | Position filter, e.g. SP, RP, C, 1B, OF, Util |
leagueKey | string | — | League key; defaults to configured league |
Parameters from the server's own tool schema.
search_players retrieves player information from the Yahoo Fantasy Baseball database to help resolve player names to player keys. It performs no mutations, deletions, executions, or financial transactions. The tool explicitly indicates it returns metadata only (name, position, injury status, ownership) without executing queries or modifying data.
From the tool's definition Tool description states it 'Find players by name' and 'Returns name, position, eligible positions, injury status, and ownership — no stats.' This is purely a search and retrieval operation with no side effects or data modification.
Attacks that exploit this kind of access
Find players by name (full or partial) and resolve them to player keys. This is the way to turn a name the user typed into the player_key that get_player_stats, analyze_player_stats, add_drop_player, and set_lineup need. Returns name, position, eligible positions, injury status, and ownership (free agent or owning team) — no stats. Optionally narrow by status (e.g. FA to only see free agents) or position (e.g. SP, OF, 2B). Returns up to 25 matches per call; page with start. It is categorised as a Read tool in the Yahoo Fantasy Baseball MCP Server, which means it retrieves data without modifying state.
search_players accepts 6 parameters: name, count, start, status, position, leagueKey. Required: name. The full parameter table on this page comes from the server's own tool schema.
Register the Yahoo Fantasy Baseball MCP server in PolicyLayer and add a rule for search_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 Yahoo Fantasy Baseball. Nothing to install.
search_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 search_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 search_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.
search_players is provided by the Yahoo Fantasy Baseball MCP server (yahoo-fantasy-baseball-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
search_players is one line of Yahoo Fantasy Baseball's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →