Get a team's roster for a date — each player's roster slot (starting position or BN/IL bench), starting status, injury status, and eligible positions, without any stats. Use this to see who is on the team and who is starting or benched. For per-date Yahoo stats use get_roster_stats; for advanced ...
AI agents call get_roster 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 |
|---|---|---|---|
date | string | — | Date as YYYY-MM-DD; defaults to today |
teamKey | string | — | Team key, e.g. 431.l.12345.t.2 |
Parameters from the server's own tool schema.
This tool performs a simple read operation to fetch roster data. It retrieves and displays roster composition and player status information with no side effects, modifications, or external operations triggered. The severity is low because misuse would only expose fantasy team composition information without financial or operational impact.
From the tool's definition Tool retrieves roster information including player positions, starting status, and injury status 'without any stats' and is explicitly contrasted with stat-retrieval tools (get_roster_stats, analyze_roster_stats).
Attacks that exploit this kind of access
Get a team's roster for a date — each player's roster slot (starting position or BN/IL bench), starting status, injury status, and eligible positions, without any stats. Use this to see who is on the team and who is starting or benched. For per-date Yahoo stats use get_roster_stats; for advanced stats use analyze_roster_stats. Defaults to the configured team and today's date. It is categorised as a Read tool in the Yahoo Fantasy Baseball MCP Server, which means it retrieves data without modifying state.
get_roster accepts 2 parameters: date, teamKey. 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 get_roster: 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.
get_roster 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 get_roster 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 get_roster. 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.
get_roster 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.
get_roster 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 →